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
NHibernate in its 3.3.1.4000 version allows to map directly to fields (mapping by code has that option). As far as I can tell, Fluent doesn't allow that right now. I'd like to add this, since it won't be too much pain. Or at least I think so. Definitely need to dig into the codebase to find if that's so. That would involve mapping primitive types, components and collections.
The text was updated successfully, but these errors were encountered:
That's my bad. Mapping directly to fields through fluent interface DOES work. Here's my example: https://gist.github.com/chester89/5455538, in case someone would need it in future. The interesting thing is - as I used a field, there's no need to mark it virtual.
The question remains open whether Fluent will allow to - a) use a complex instance (with properties and stuff) as a non-public field and b) use same scenario for components
No, it doesn't work with components. Tried two scenarios - private field mapped as a component which has public properties, private field mapped as a component which has private fields. What's really strange is that in second case, I think correct hbm mapping was generated, but NH still can't find a property with a component name. Sad.
NHibernate in its 3.3.1.4000 version allows to map directly to fields (mapping by code has that option). As far as I can tell, Fluent doesn't allow that right now. I'd like to add this, since it won't be too much pain. Or at least I think so. Definitely need to dig into the codebase to find if that's so. That would involve mapping primitive types, components and collections.
The text was updated successfully, but these errors were encountered: