On Fri, 13 Apr 2007, Greg Monroe wrote:
One thing to keep in mind as you're modifying this is the long term request/idea of separating out the Torque "schema" name function that DBName does from the DB connection function.
That was what I meant by "second step" :-)
I.e., you should be able to compile the OM once and use this with multiple connections. For example, doing some sort of copy between DB servers or an app with different users accessing their own database area. Probably beyond the scope of what you're playing with but if you see an easy way to do this...
I'd rather not do this between RC's
If I remember right, a big problem in this is that there are a lot of areas where objects are created without access to criteria / connection info. These are the problem area, since it defaults to the compiled DB connection info.
The idea would be to use Torqie.getDefaultDB() instead of DATABASE_NAME in all places expect where the DatabaseMap is accessed. Not too difficult, one just has to look at every usage of DATABASE_MAP.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
