Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct FlatTableProjection being called FlatFileProjection #3629

Merged
merged 1 commit into from
Jan 16, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/events/projections/flat.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,9 +161,9 @@ public class FlatImportProjection: FlatTableProjection

A couple notes on this version of the code:

* `FlatFileProjection` is adding columns to its table based on the designated column mappings.
You can happily customize the `FlatFileProjection.Table` object to add indexes, constraints, or defaults.
* Marten is able to apply schema migrations and manage the table from the `FlatFileProjection` as long as it’s registered with Marten.
* `FlatTableProjection` is adding columns to its table based on the designated column mappings.
You can happily customize the `FlatTableProjection.Table` object to add indexes, constraints, or defaults.
* Marten is able to apply schema migrations and manage the table from the `FlatTableProjection` as long as it’s registered with Marten.
* When you call `Map(x => x.ActivityType)`, Marten is by default mapping that to a snake_cased derivation of the member
name for the column, so “activity_type”. You can explicitly map the column name yourself.
* The call to `Map(expression)` chains a fluent builder for the table column if you want to further customize the table
Expand Down
Loading