Hello Tim, I'm dying to start using prepare_cached, but thus far the risk has always seemed too great. I never heard about this again after this discussion, and I'm not aware of any resolution or any version of DBI in which prepare_cached is safe. I'm sorry to bother you directly but I have exhausted my own resources to figuring this out.
Can you please advise? Thank you, Paul ----- Original Message ----- From: "Stephen Clouse" <[EMAIL PROTECTED]> To: "Tim Bunce" <[EMAIL PROTECTED]> Cc: "dbi-users" <[EMAIL PROTECTED]> Sent: Thursday, February 28, 2002 5:16 PM Subject: Re: [PATCH] Optionally prevent prepare_cached from calling finish on active handle -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Feb 28, 2002 at 10:21:32AM +0000, Tim Bunce wrote: > Umm, here's another thought... > > How about changing prepare_cached so it includes the caller() info > in the hash key by default. That way prepare_cached won't return > the same statement handle if called from two different places even > if the $statement is the same. The other way was easier :) Also wouldn't work in our case -- we have an additional abstration layer for the database, so prepare_cached's caller will always be the same. This seemed to be the most application-independent method of solving it (that is, don't touch it and let the application deal with it). - -- Stephen Clouse <[EMAIL PROTECTED]> Senior Programmer, IQ Coordinator Project Lead The IQ Group, Inc. <http://www.theiqgroup.com/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjx+nioACgkQA4aoazQ9p2eiegCg5wJ/CjtJko6No7qRlRwkY10g 0coAmwWS3BXSXXbLqArq9cXESuwxnEfJ =Bt+K -----END PGP SIGNATURE-----
