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
I'm an Orchard developer and in Orchard, AutoMapping can add dynamic fake relationships because of the old Fluent API. In the latest version of FluentNhibernate, "References" methods require expressions which prevents creating dynamic relationships.
Say for instance, in Orchard there is a "ContentItemRecord" class , and each module creates a "PartRecord" table. Then Orchard creates dynamic ManyToOne references on ContentItemRecord for each PartRecord mapped by each module.
This may indeed be a requirement for many modular projects. I've added a new "References" method on the ClasslikeMapBase class which gets a propertyName as a string parameters and calls the "ManyToOnePart References(Member member, string columnName)" method using a DummyPropertyInfo instance.
I've achieved migrating Orchard to FluentNHibernate's latest release with this but I'm not sure this is the right place to make this change.
The text was updated successfully, but these errors were encountered:
I'm an Orchard developer and in Orchard, AutoMapping can add dynamic fake relationships because of the old Fluent API. In the latest version of FluentNhibernate, "References" methods require expressions which prevents creating dynamic relationships.
Say for instance, in Orchard there is a "ContentItemRecord" class , and each module creates a "PartRecord" table. Then Orchard creates dynamic ManyToOne references on ContentItemRecord for each PartRecord mapped by each module.
This may indeed be a requirement for many modular projects. I've added a new "References" method on the ClasslikeMapBase class which gets a propertyName as a string parameters and calls the "ManyToOnePart References(Member member, string columnName)" method using a DummyPropertyInfo instance.
I've achieved migrating Orchard to FluentNHibernate's latest release with this but I'm not sure this is the right place to make this change.
The text was updated successfully, but these errors were encountered: