Map it as a separate entity then, CustomerAddress.
public class Customer {
public virtual CustomerAddress Address { get; set;
}
public CustomerMap() {
References(x => x.Address);
}
On Fri, Feb 13, 2009 at 10:31 PM, Craig G <craig.gold...@gmail.com> wrote:
>
> I've been looking at the underlying NHibernate feature and came to the
> same conclusion. Unfortunately we don't have any control over the
> schema because it is a legacy database.
>
> Thanks for the reply James.
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@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
-~----------~----~----~----~------~----~------~--~---
