-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> DBD::Oracle does not implement placeholder binding by > re-writing statements itself. Instead it uses Oracle's > internal implementation of placeholders. Yes, unfortunately PostgreSQL does not support the use of DEFAULT inside of its server-side prepared statements either. However, someday it will, and DBD::Pg will be ready! :) Currently, if any of the values (e.g. the xeecute() array) is a DEFAULT value, DBD::Pg switches transparently back to the old style of prepared statements by doing the placeholder substituting itself, and then sending the computed string to the backend to be executed. So, we potentially lose a tiny bit of speed but allow people to not have to create a separate statement handle (which they can still do of course, if performance becomes that much of an issue). > So - my point remains. DBD::Oracle, as designed, cannot > implement the suggested feature. Well, I don't think it will actually involve any shared DBI logic code, but I would like to see a common syntax used, e.g. something like $DBI_DEFAULT. Drivers would be free to have their dbdimp.c take advantage of it or not. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200604281323 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFEUk/NvJuQZxSWSsgRAj24AKD0R8hOCKQd4wb8vV0XUr3Wr4+xjQCcCdUj smeCkeJKYWHdDOoVncib6mU= =wIpH -----END PGP SIGNATURE-----
