On Aug 9, 2:47 am, Diego Mijelshon <[email protected]> wrote: > If they are related and you want to tream them as such, make them related in > the model.
I can't. It violates the requirement I have been given. Whether you agree with the requirement or not, you surely have to concede that if the requirement is there then it must be met, else you don't get paid. How can one make a extension model if every time you want to add an extension you have to change the base to know about the extension? By that definition, the only way I can conceive doing that would require a source branching strategy. Source branching strategies are not code and cannot be tested as code. And do not meet the requirement. On Aug 9, 2:47 am, Diego Mijelshon <[email protected]> wrote: > You say "the IDs are the same, which means there is an obvious left-join > that can be made" but provide no way for NH to know that. And therein lies the rub. I know they are. You can see from the code that they are. They are because the 'contract' says that must be and a database foreign key constraint says that they will be. Why can I not tell NHibernate that they are? Why should NHibernate even care? -- 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.
