commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pramodh Peddi" <>
Subject useServerPrepStmts and jdbcCompliantTruncation for MySQL with dbcp
Date Wed, 15 Jun 2005 20:23:31 GMT

I am introducing apache's DBCP tool into our product, which uses MySQL.
Till now, we used different mysql specific properties in the db url. The
url we used is:
Stmts=false&jdbcCompliantTruncation=false". And while making dbcp work,
this is the exactly the same URL I gave to


tmts=false&jdbcCompliantTruncation=false </value>



in Tomcat's server.xml. When I start tomcat, it complains saying "The
reference to entity "useServerPrepStmts" must end with the ';'
delimiter". And when I removed useServerPrepStmts from the URL, it
started complaining the same thing about jdbcCompliantTruncation. 


Can we not use these properties when I use apache's DBCP tool?
"useServerPrepStmts" can be achieved because DBCP tool itself has
poolPreparedStatements, which can be defined in server.xml. But what
about other many useful properties offered by MySQL/MySQL-Connector-J?


Thanks in advance,



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message