How about renaming both classes? If they are different databases, I assume that
they are different kinds of users. So XxxxUser and YyyyUser seems appropriate.
Just "User" would be a bit ambiguous, I think.
Tony
-Original Message-
From: Borut Bolčina [mailto:borut.bolc...@gmail.com]
Sen
Hi Borut, you may want to look at my copying DataMaps example:
http://cwiki.apache.org/CAY/copying-datamaps.html
It is old (still references "objectstyle" instead of "apache", but
might work fine with minor changes (like changing the package name).
(I haven't tried it on Cayenne 2.x+ yet.)
I was
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
> 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,
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 Adamchi
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
> You have to place them in different DataDomains and use separate contexts
> to access them. Or call your class UserSomething (whi
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
