Hi Rob, I have faced the same problem and use patched Peer.vm and MapBuilder.vm sources. So would like to see a kosher solution for 2.4. (or 2.3x).
It seemed easier to leave DATABASE_NAME in place but initialise it with a static getDatabaseName() method. I did this with a method outside Torque but should have used Torque.getDefaultDB(). Then add a line to build.properties e.g. "torque.useRunTimeDefaultDatabaseName = true" which defaults to false. So unless this is set the existing code is generated. If using the torque default database name is dynamic enough for you I will change the vm's to do just this and submit the patches to the dev list. Regards, Malcolm Kendall -----Original Message----- From: Scott Eade [mailto:[EMAIL PROTECTED] Sent: 06 January 2004 04:50 To: Apache Torque Users List Subject: Re: Torque with more dynamic DB connections... Rob Gordon wrote: >Will do...as you can imagine, things are not quite always like they appear. As >I look >at it, the change touches more and more code. Not absolutely foreboding, but >bigger >than expected. As always. > > This is where feedback from someone with more experience than I would be of help to you in that they could perhaps advise you of potential problems on your way down this path. >You say, "In the absence of any strong objections..." Would that mean >existing >committers/developers responding to my post? > > Yes, this is what I mean. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
