... >> >> When Turbine initializes, it comes up with one database connection pool >> named 'default'. My database is named 'ANALYSEN', though, in the >> analysen-schema.xml file. Hence, I could never get the OM complex to work >> at all. I run Torque/OM separated from Turbine.
>Torque creates a pool and assigns it to whatever name you use, it will >only create a pool named 'default' if you use that handle in specifying >the connection pool properties. [...] >I assume you deleted the connection pool named 'default' as you have no >need for it. I do not understand why you say Turbine did this when it >is only creating connection pools you have specified in your properties >file. Ah, now I finally do see. I have been staring a lot at the TurbineResources database parameters but not been able to make heads or tails out of them for some reason. I never actually thought that the "database.default.xxx" really meant "database.<databasename>.xxx". I made the assumption that it meant a default configuration more in technical terms rather than (also) database instance naming. Silly of me, really! Sorry! <huge sheepish grin>... To my meagre defense I must add that I rarely use more than one database at a time. My first misstake in this case seems to have been assigning a name to the database in the schema XML-file. I thought that was more like a comment than having actual meaning in the generated code. If I hadn't done that I would have been able to go with the 'default' (which I misinterpreted completely, my second misstake) in TurbineResources. [...] >where DATABASE_NAME in your case is going to be ANALYSEN. It seems this >code should be moved outside the null check. Are you passing in a >connection to FooPeer.doSelect? Otherwise setting the correct dbName >should be handled by the code given above. Yes, I did have to pass a connection before I tried using setDbName and then finally saw that I could create criteria (new Criteria(<databasename>) under the proper name. But then, thanks to you, I now know what I did wrong in the first place! :-P So, now I've replaced 'default' with 'ANALYSEN' in TurbineResources, done away with allocating separate database connection handles and I'm no longer setting database name in Criteria and it works beautifully! I will, however, remember this on that day when I *do* have to deal with more than one databse at the same time! :-P Thanks a mil for your help, John McNally! ;-D Regards Per ___________________________________________ Per Sten Software Engineer Integris Svenska AB Karlsrov�gen 2D PO Box 544 SE-182 15 Danderyd Sweden E-mail : [EMAIL PROTECTED] Phone : +46 8 622 42 76 Cellular: +46 70 921 42 76 Fax : +46 8 622 42 23 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
