Hi, I have
class Foo IList FooBarRelations class Bar class FooBarRelation bool IsSpecial bool IsNotSoSpecial bool IsSomethingElse .... I always hated this relation object as it makes lots of things cumbersome and prone to n+1. Now, out of domain changes, I can just do class Foo IList SpecialBars IList NormalBars because it turned out that these were the only two cases actually needed (YAGNI). So I can map this just to 2 many-to-ones and be happy. Still I have all those booleans in the table, that would allow me to place a where clause in the many-to-one mapping and would not have to touch the db for the domain change. 1) would you do this, or go for a separate table? 2) If I would just keep the table and used the where clause in the mapping, would this also write the correct value on insterts/updates or is this read only? -- Jan ___________________ [EMAIL PROTECTED] www.limpens.com +55 (11) 3082-1087 +55 (11) 3097-8339 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
