I have the following use case: I want to define optional
subsets (read "services") for my app. Some of these subsets
use tables to do their stuff. So, I end up with
serviceA-schema.xml
serviceB-schema.xml
serviceC-schema.xml
etc.
Now, I would like to defer defining the database name for
each of the subsets, so that I can define them in TR.props.
That way, I would be able to put them all in one DB, or
separate DBS:
serviceA.database = DB1
serviceB.database = DB1
serviceC.database = default
Is this even possible? I remember that at some point it was
mandatory to start the schema.xml file with
<database name="foo">
and it was not possible to switch that database name to something
else on the fly. Is this the way things still work, or can I
just not declare a database name and set one dynamically when
I set up my Criteria objects?
One way out could be to define separate DBs in TR.props, and have
one or more of them point to the same JDBC connection, but I
think that would put multiple connections to the same DB in the
pool, right?
Thanks for any hints,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
