I'd say that is a requirement. We have some internal jsp web pages that we point to different Oracle instances, and we would be unable to use torque as the infrastructure because of that. Furthermore, it would be impossible to migrate an application through a development/testing/deployment cycle without reconfiguring and recompiling (assuming of course that there are distinct database instances devoted to each phase) and I suspect that most QA policies might not allow that.
-----Original Message-----
From: Sam Joseph [mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 08, 2002 5:58 AM
To: Turbine Torque Users List
Subject: Re: Why is the database name hardcoded EVERYWHERE?
Andrew wrote:
>Ok, thanks for clarifying that.
>
>Here's a scenario:
>
>I generate the OM classes with a database name of "foo". Then I change
>the database name everywhere to "bar". When I run what will happen? I
>suspect it will try to look for the "foo" database and find nothing.
>
>This is what I found so grievous. Am I wrong?
>
I'd have to say yes. If you change your database name on the DB, then
you update the Torque and build properties file and then you just run
ant again and rebuild the XXXPeer classes. Then the system will work
fine with your renamed database.
Admittedly you can't swap over the database name and reconnect to it
without recompiling your classes, but since you can recompile them all
with a single command, it doesn't seem so grevious.
Do you have a paritcular need to change database names on the fly? If
you do then we might be able to have a discussion about how to support that.
CHEERS> SAM
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
