Re: pdo bindParam() with named parameters

On another note after working with PDO a bit, a debugging output at some level would be extremely valuable and help with adapting. Not knowing what's being sent by Execute, regardless if it's relying on backend assembly or not is a big hindrance. Are there serious technical roadblocks to offering some sort of callback to find out whats being sent before or after execute? Maybe a pseudo execution that dumps the internals? Gavin On Fri, 11 Feb 2005 08:36:17 +0100, Lukas Smith <lsmith@php.net> wrote: > Wez Furlong wrote: > > On Fri, 11 Feb 2005 00:59:50 +0100, Edin Kadribasic <edink@emini.dk> wrote: > > > >>You know that changing this after 5.1 release and official introduction > >>of PDO would be impossible. > > > > > > It's always possible to relax restrictions after a release, rather > > than tighten them. > > Well I think this would considerably increase confusion even more if we > provide both options. Anyways I really dont see the performance argument > here. I think we are basically pitting: > > clarity vs. number characters to type > > I think PHP has historically taken "clarity" first. This will ease the > work for anyone writing code on top of PDO even if that makes examples a > bit longer to type out. However isnt writing code on top of PDO the > actual intention of this ext to begin with (versus having great short > examples)? Furthermore I think for the vast majority of uses it will > actually be less characters (1 character per parameter) to type given > the proper selection of the default for queries containing named parameters. > > Another note: > I have seen people claim thatprepare/execute is an advanced feature that > novice users shouldnt be using anyways. The PDO API really pushes people > towards prepare/execute. Also every PHP security article/talk these days > tells people that prepare/execute are the silver bullet against SQL > injection. > > regards, > Lukas > > -- > PECL development discussion Mailing List (http://pecl.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >