How do you prevent multiple rows with the same value and time? Or multiple rows with the same time? Or if you allow these duplications, what does it mean? Not sure about your requirements, but to allow several rows which are exactly the same seems strange to me.
It seems that you could have either PRIMARY KEY (Time), or PRIMARY KEY (Time, Value), which would be handled by NHibernate as any other key, or composite-key in the latter case. What would you gain by not having either of these as primary key? So, for question #1, yes you don't need to have a third column, if you can use one or both of the columns you already have as primary key. As for question #2, how do you suggest that another entity should reference the Result object if there is no primary key at all? If you want to have PRIMARY KEY (Time, Value), what you really have is a value object, not an entity. /Oskar 2009/4/16 kor <[email protected]> > > in my 1) question yes, i don't need a primary key at all, > i have only a result object wich contains simple data without any > constraints on it (as unique on some columns, foreign-key, etc) > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
