Thanks. It did not make sense until I read the part "J2EE Prepared Statement Cache".
--- Ramakrishna Kuppa <[EMAIL PROTECTED]> wrote: > I think we are talking of two different things here: Whether you > create a > connection OR pick one from pool, by using the PreparedStatement, > you avoid > repeated compilation of the SQL statement. > > A good explanation on this is available at > http://www.theserverside.com/resources/article.jsp?l=Prepared-Statments > > - Ramakrishna > > -----Original Message----- > From: Jason Kilgrow [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 10, 2002 1:37 PM > To: JDJList > Subject: [jdjlist] PreparedStatement > > What would be the advantage of using a PreparedStatement rather > than > a Statement if I'm using connection pooling? > > I know that the PreparedStatement is precompiled but in my > environment, I typically get a connection from the pool, execute my > query, process my results, and then free the connection all in one > method. So, if I were using a PreparedStatement, wouldn't the query > in the PreparedStatement need to be compiled every time the method > is > called anyway? > > __________________________________________________ > Do You Yahoo!? > Yahoo! Shopping - Mother's Day is May 12th! > http://shopping.yahoo.com > > To change your membership options, refer to: > http://www.sys-con.com/java/list.cfm > > > To change your membership options, refer to: > http://www.sys-con.com/java/list.cfm > __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com To change your membership options, refer to: http://www.sys-con.com/java/list.cfm
