Another guess is that modern database do a pretty good job of caching queries at the server, so why not let the database server do the caching for you?
-----Original Message----- From: Anurag Kapur [mailto:[email protected]] Sent: Wednesday, February 25, 2009 3:43 PM To: Commons Users List Subject: Re: [dbcp] poolPreparedStatements parameter Just guessing, Probably because PreparedStatements are not used in many applications and thus by having the pooling option turned off by default it saves the overhead involved in maintaining the pools. Can a expert validate by guess and if it is not correct provide a sane explanation? :) Cheers Anurag ------------------------------------------------------------------ Anurag Kapur Associate - Technology, Sapient Corporation India. http://www.linkedin.com/in/anuragkapur ------------------------------------------------------------------ On Wed, Feb 25, 2009 at 9:49 PM, Stefano Nichele <[email protected]>wrote: > Hi All, > I would like to ask why poolPreparedStatements is false by default. It > seems that setting it to true could improve performances (I haven't > tried it, but it seems useful) Is there any drawback or known issues ? > > thanks a lot > ste > > --------------------------------------------------------------------- > 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]
