Generally speaking, if you were using most SQL databases the approach would be to use a stored procedure. The stored procedure compilation saves the various query plans as part of the data of the stored procedure. I doubt MySQL does it, but you could ask on their development list.
George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > From: Khawaja Shams [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 12, 2006 2:19 PM > To: Tomcat Users List > Subject: PreparedStatement w/ Connection Pooling > > Hello all, > I am working on a web application that will manage > assignments/students/classes for the teachers at a school. > Most of my pages > in the application need to access our mysql database very > frequently. For > this and for other security reason, I would like to use > preparedStatements. > However, from what I understand, preparedStatement are > prepared on top of a > connection. If I am using connection pooling, this seems to > be useless for > performance as I would be preparing a statement each time I get a > connection. Is there any way to get around this? Is there > such thing as a > preparedStatement pool? Would you recommend implementing this > on my own? > Thanks for your time and help. > > > Best Regards, > Khawaja Shams > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
