Clean up handling of multiple columns #74

jagregory opened this Issue Jul 21, 2011 · 0 comments


None yet
1 participant

jagregory commented Jul 21, 2011

If the user defined a mapping as follows:

HasMany(x => x.Children)
  .KeyColumns.Add("one") .Unique() .KeyColumns.Add("two");

Then the behaviour is to have two column mappings created, each with the unique set to true. This is somewhat counter-intuitive. It would be better to handle multiple columns with something like

.KeyColumns.Add("name", c => { optional column mapping });
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment