Thanks for the advise Chris, shouldnt there be any pooling specific parameters here, like pool-max-size and the like ?
> Sure oracle is for the rich people, but postgres is free. As for MySQL pooling > I'm not sure but I thought support for pooling was kind of expected for drivers > to conform to JDBC 2 onwards (could be wrong here though). Just have a look > through the driver .jar file you have for MySQL and see if you can spot > something which suggests it might be a pooling implementation class. I guess > tomcat pooling is needed if you can't get your hands on a driver that does it > for you. > > As for the repositiory.xml bit that is relevant, an example is: > > <jdbc-connection-descriptor > platform="Oracle" > jdbc-level="2.0" > driver="oracle.jdbc.pool.OracleConnectionCacheImpl" > protocol="jdbc" > subprotocol="oracle:thin:@cumae.ebi.ac.uk:1531" > dbalias="ZPRO" > username="intactweb" > password="***" > /> > > > Chris > > Lukas Severin wrote: > > > I read it was not ready for prime time yet - though I was hoping that it > > will soon be ... > > (simple queries and inserts work just fine now). Im not using Oracle as db > > (if I had I guess the project would consider a few thousand dollars for a > > commercial JDO peanuts :) > > > > Interesting point about JDBC2.0 drivers. That sort of make tomcats pooling > > obsolete then ? > > Im using MySQL type 4 driver, Id better check this out then... Do you know > > if they support pooling ? Can you show a snippet of repository.xml showing > > this ? > > > > Thanks ! > > > --------------------------------------------------------------------- > 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]
