Map(x=>x.YourProperty, "ColumnName").Access.Using<YourCustomAccessorType>();
Alternatively, you might want to check into IUserType to see if you can get default values going that way to a legacy DB. Although I admit, the custom propertyaccessor seems like a much better fit for providing default values. On Wed, Feb 17, 2010 at 9:08 AM, Alex McMahon <fluxmu...@gmail.com> wrote: > I'm working with a legacy database and am trying to isolate the messy > stuff from my domain model. > > I've been looking at using custom IPropertyAccessors to provide > default values for legacy columns. The link below shows my inspiration > for this... Can anyone tell me how to convert the hbm on the linked > page to fluent mappings? > > http://elegantcode.com/2009/07/13/using-nhibernate-for-legacy-databases/ > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To post to this group, send email to fluent-nhibern...@googlegroups.com. > To unsubscribe from this group, send email to > fluent-nhibernate+unsubscr...@googlegroups.com<fluent-nhibernate%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > > -- - Hudson http://www.bestguesstheory.com http://twitter.com/HudsonAkridge -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibern...@googlegroups.com. To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
