that would be fine if the model was static, we didn't use a nice gui modeling tool and users weren't going to create subclasses.
I respectfully disagree, since I feel it is more consistent to always include the discriminator column in the column list of the select statement. excluding it feel like a special case logic in NH to me. peter On Sep 26, 3:38 pm, "Ayende Rahien" <[EMAIL PROTECTED]> wrote: > Using a where="" is the appropriate action here, not a discriminator. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
