… The .Not operator wasn't working when used from within the HasManyConvention.
1.1 introduced a regression where entities that are the target of multiple Reference mappings from the same source would end up with multiple key columns being defined based on the property names. The source of this was the RelationshipKeyPairingVisitor, which frankly I have no idea what it was trying to do. I think it might have something to do with composite keys and relationships, but the usage isn't very clear. For the time being I've removed this functionality.
…and fixed it to use mspec.
…o the underlying ExternalComponentMapping. Also modified ExternalComponentMapping to prevent it from running a visitor more than once." This reverts commit 35609a0.
…derlying ExternalComponentMapping. Also modified ExternalComponentMapping to prevent it from running a visitor more than once. This combination of changes should allow conventions to be applied to members of a component that was mapped via ComponentMap.
…s to be set via conventions
…Mapping as a default only, so that a convention can override the value.
…ribute of a nested composite element to the xml.
…l the xml nodes so it could re add them (in the correct order), but it only removed half of them.
Updated the References and HasOne methods to include support for no-proxy lazy loading. This is done through an overload with a Laziness parameter, to avoid breaking changes. LazyLoad(Laziness.NoProxy); The Laziness class can also be instantiated by the user with their own value; this will be handy for if NHibernate adds any more values to this enumerable before we can catch up. Fixes #183
Also updated docu
Column prefixes weren't being applied to nested components due to the hacky way they (prefixes) were implemented. I've now removed all the component prefixing from the automapper and updated the ColumnPrefixVisitor to work on all components rather than just ComponentMap's. Fixes #180
When using automapping, if you specified a discriminator in an override it was ignored due to the SubclassStrategy taking precedence. I've removed SubclassStrategy entirely in favour of using just IsDiscriminator. This is a breaking change, but should be easy for people to fix up.
When using mixed KeyReference and KeyProperty's in a CompositeId mapping, the order that you called them in wasn't being respected. This has needed a refactor of the compositeId model, to store those two mappings in a single collection to respect the order. Fixes #163