-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
PostgreSQL has recently added a true server-side prepare, which
raises some issues in regards to the prepare/execute DBI model.
Our initial thought was simply to use the new prepare/execute
when it was available on the backend, and keep everything
transparent to the user. However, there are cases where a
local (or non server-prepared) prepare is preferred, so we need
to allow both. One idea I had, which Rudy Lippan also thought
of for DBD::mysql, is to have a global and a local flag to toggle
between the two. The global can be set at connect and resides
at the $dbh level. The local is an extra attrib send to the
prepare() method, which would override the global method. Toggling
between the two *after* the prepare would even be possible,
especially if you have an intelligent app that realizes that
it may need to mix and match them.
Has anyone else run into this? Does the above sound like a good
solution? (The 'local' prepare for DBD::Pg just means that we
build the complete SQL statement ourselves and send that off
to the server).
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200402221153
-----BEGIN PGP SIGNATURE-----
iD8DBQFAON9uvJuQZxSWSsgRAq4YAJ4jFuHkwx0oCUkd0dBvIb52Yk9+qACdEGyA
daEGCBw9waTKBpJod7ZxyxE=
=3php
-----END PGP SIGNATURE-----
