Yeah, it is usage patterns that I miss in the documentation. Luckily for me, this list is very responsive! Thanks.
2009/6/16 Andrus Adamchik <[email protected]> > Isn't this a better scenario? >> > > > It all depends on your app I guess. > > Andrus > > > > On Jun 16, 2009, at 2:05 PM, Borut Bolčina wrote: > > OK, I will try to use two different data domains, after all, the databases >> are completely unrelated. Isn't this a better scenario? >> >> -Borut >> >> 2009/6/16 Andrus Adamchik <[email protected]> >> >> You have to place them in different DataDomains and use separate contexts >>> to access them. Or call your class UserSomething (which looks like a more >>> sensible way to me to resolve a naming conflict). >>> >>> Andrus >>> >>> >>> On Jun 16, 2009, at 1:03 PM, Borut Bolčina wrote: >>> >>> Hi, >>> >>>> >>>> is it somehow possible to have two DomainNodes (2 different independent >>>> databases) with the same entity/class name? Both databases have table >>>> (entity) "user" and I don't want to rename one class to UserSomething. >>>> >>>> Regards, >>>> Borut >>>> >>>> >>> >>> >
