Skip to content

Commit

Permalink
Correct FlatTableProjection being called FlatFileProjection
Browse files Browse the repository at this point in the history
  • Loading branch information
jakobt authored and jeremydmiller committed Jan 16, 2025
1 parent e27c15e commit 27e5e34
Showing 1 changed file with 3 additions and 3 deletions.
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

0 comments on commit 27e5e34

Please sign in to comment.