You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NH-3114 - Collection inside Component cannot be mapped to a different table (#691)
* NH-3114 - create a few test cases
The first test verifies mapping-by-code generates a correct mapping, while
the second test inserts an entity with the first component set but currently
also gets the second component collection initialized with the same contents
after retrieving.
This fixture is providing explicit column- and table-names to make sure
everything ends up where we expect it.
* NH-3114 - include the full property path in collection mappings
Since PropertyPath is used as dictionary key during mapping/customization,
only considering the local part may lead to customizations being applied to
the wrong members (or being applied multiple times, leaving only the last
invocation each as effective result).
With the parent path included, collection mappings on nested contexts (such
as components) now work properly even when the nested context is repeated
on the same type (such as having multiple properties of the same component
type on a root or subclass).
thrownewMappingException(string.Format("Wrong collection element type. For the property/field '{0}' of {1} was expected a dictionary of {2}/{3} but was {4}/{5}",
0 commit comments