Re: PDO->execute() addition

My personal opinion on this, is that bindColumn is something that will be used a lot less than real bindParam, as it doesn't provide as much utility; it's purely a PHP-side aliasing operation to magically set variables from the columns of the rowset. I believe that explicit bindColumn() calls make this "magic" more clear, and this sentiment is backed up by some of the initial negative vibes about the whole bindParam/bindColumn idea. I don't believe that not adding a bindColumn() shortcut means that we should remove the bindParam() from the execute call, nor that the current implementation is "half breaded". From a keeping-a-somewhat-clean-api-for-the-future perspective, I'd like to avoid overloading the execute() call, unless there is very strong demand for it, so I asked Marcus to post his suggestion here. If you think that we should add a bindColumn shortcut as an optional second parameter to PDOStatement::execute(), please pipe up. --Wez. On 5/24/05, Marcus Boerger <mail@marcus-boerger.de> wrote: > Hello guys, > > currently PDO::execute() allows to bind parameters by specifying them > in an associative array and pass that as first parameter to execute(). > Now what i'd like to do is allowing to bind the result columns by passing > a second associative array. Without this addition i think we should remove > the ability to bind parameters to since it is strange to support a half > breaded feature that was meant to simplify the handling. Any comments? > > > -- > Best regards, > Marcus mailto:mail@marcus-boerger.de > > -- > PECL development discussion Mailing List (http://pecl.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >