Re: bind_param for named parameters - clarification sought

2008-05-14 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 >> I believe, but am prepared to be put right, other non-perl database drivers >> also drop the ':' when binding. > Any other driver authors/users care to comment? FWIW, DBD::Pg requires a leading colon, but strongly encourages the use of "$1"

Re: bind_param for named parameters - clarification sought

2008-05-13 Thread Jonathan Leffler
On Tue, May 13, 2008 at 10:13 AM, Tim Bunce <[EMAIL PROTECTED]> wrote: > On Tue, May 13, 2008 at 01:20:14PM +0100, Martin Evans wrote: > > Tim, > > > > In the thread "problem with DBD::ODBC and placeholders > [SEC=UNCLASSIFIED]" > > on dbi-users recently you said: > > > > > Drivers that support na

Re: bind_param for named parameters - clarification sought

2008-05-13 Thread Tim Bunce
On Tue, May 13, 2008 at 01:20:14PM +0100, Martin Evans wrote: > Tim, > > In the thread "problem with DBD::ODBC and placeholders [SEC=UNCLASSIFIED]" > on dbi-users recently you said: > > > Drivers that support named placeholders like ":N" where N is an > > integer, could support both forms of bindi

bind_param for named parameters - clarification sought

2008-05-13 Thread Martin Evans
Tim, In the thread "problem with DBD::ODBC and placeholders [SEC=UNCLASSIFIED]" on dbi-users recently you said: > Drivers that support named placeholders like ":N" where N is an > integer, could support both forms of binding: bind_param(":1",$v) and > execute($v) > It's not dis-allowed. Driver