> -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 >> Here's the short version of my question: >> Is there a way to have a statement handle cache shared >> among 2 or more database handles?
> Here's the short answer to your question: No > In addition to DBI problems, you'll have database level problems as well, > as many databases do not allow sharing of (true) prepared statements, > temporary > tables, and other such things across sessions, and certainly not across > actual databases. > I'm not seeing the problem in having 40 statement-level caches, unless you > have an insanely high number of prepared statements. One optimization you > could do is to prepare as many of them up front as possible on the initial > connection, although that may throw off an LRU if they don't all fit > in memory. So make them all fit in memory. :) > - -- > Greg Sabino Mullane [EMAIL PROTECTED] > End Point Corporation > PGP Key: 0x14964AC8 200806121332 > http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 > -----BEGIN PGP SIGNATURE----- > iEYEAREDAAYFAkhRXd8ACgkQvJuQZxSWSsjLmQCfTvAN7rzR/jgj5xgur1Y5PN6l > q+4AoJbiycnM7zO701BlNeEUtm+FgzhB > =6yc5 > -----END PGP SIGNATURE----- I see. We use DBD::Oracle, and so if that creates (true) prepared statements, then it's out of our hands as OCI is cooperating with our statement preparation. I thought that it was just statement preparation fully within DBI/DBD::Oracle and not within OCI as well. -- Eric Simon
