Ok. I think it makes sense now. Obviously, I was hoping that NHibernate could facilitate this through overriding of the ID since I know that my Form.ID and Form.PublicationID would yield a unique record for my application but just using different values. I completely understand the principles you are conveying and I don't disagree rather just hoping this was possible as I've worked on several non-ORM applications where the data model was standardized in this way with non-natural PKs on each table. I'll push for the data model changes then to fascilitate this :-)
Thanks everyone! On Sep 23, 4:42 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/9/23 Ken Egozi <[EMAIL PROTECTED]> > > > you must use the same PK for the base and derived tables, at least as far > > as NH is concerned. > > Correct and it is a basic concept of ORM. > > @Scott > To understand it better we must speak about what ID mean. > With ID we mean POID: persistent object ID. > Each object have an ID; in RAM (transient) the ID is the reference of the > instance, when you persist an instance you are assigning a new ID to that > instance: the POID. > > Now... suppose you have Animal<--Dog<--Fiamma (Fiamma is my Schnauzer) > If I have Fiamma, how many instance I have ? only one and I have only one > POID (Fiamma is a Dog and a Dog is a Animal) > Only one object = only one POID > > Many times we are misunderstanding inheritance with role. > Fiamma is a Dog > or > Fiamma can work as watchdog > > -- > 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 -~----------~----~----~----~------~----~------~--~---
