Hi Avi,
Sorry I forgot to respond to this the other day... I was just in the
midst of integrating the Transactions code at the time.
At 6:54 AM -0700 5/29/00, Avi Cherry wrote:
>Town SHOULD be able to handle multiple databases at the same time,
>in the same classloader context, shouldn't it?
Well, it SHOULD, but perhaps I made a mistake that prevents it :6.
Specifically, there are a bunch of static variables in the generated
_DB.java. How are you initializing and/or calling the two databases?
Are you actually instantiating two DB objects somehow? Have you
modified the generated DB.java and/or _DB.java?
Oh, I just found my comment with the idea of generating a separate
source tree for each database, e.g. putting the two ormaps in
separate packages. That should work. Is that what you did?
Schemas, once generated, are stored in a static hashmap by table
name. If by chance your two DBs have tables with the same name but
different structure, that would explain the problem. I should fix
that in any case.
Besides the Schema hashmap, nothing else of relevance is static in
all of Town. So, except for that problem, the two DBs in a single
JVM shouldn't affect each other at all.
The only other consideration there (but not related to the present
problem) is that there's just one heap for the object cache that
Table keeps, so cacheCleanupThreshold is static (so in your case it
will be set to the value in the conf file of the DB you load last).
Hope this helps...
-David
________________________________________________________________________
David Soergel .oooO Oooo. "Music and Living----"
123 Forest View ( ) ( ) "The same thing," said Pooh.
Woodside, CA 94062 \ ( ) / [EMAIL PROTECTED]
(650) 303-5324 \_) (_/ http://www.lorax.org
________________________________________________________________________
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
