ORM (object relational mapping):The POID should be unique inside a class hierarchy or, even better, inside your domain. A POID should refer uniquely one, and only one, entity instance.
How look your domain? 2009/9/23 Patrik Lowendahl <[email protected]> > Is there any plans on supporting joins mapping on any other column then the > class PK? > > I see a lot of legacy where they have used arbitrary columns as the FK, > like this example: > > [Person] > PersonId > > [AdPerson] > PersonId > ObjectSID > > [User] > ObjectSID > > Doing a projection over this (UserInfo) becomes bothersome and the simplest > solution would be something like: > > <class name="AdPerson"> > ... > <join table="Person"> > <key column="PersonId" /> > ... > </join> > <join table User> > <key column="ObjectSID" foreign-key="ObjectSID" /> > --- > > For the record, I don't agree with the database model, but this is what I > have to work with and a construct like the above would make it a lot more > easy to manage. > > -- > Patrik > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
