ID:               40740
 Comment by:       weblab dot solutions at gmail dot com
 Reported By:      phpbugs at filofox dot com
 Status:           No Feedback
 Bug Type:         PDO related
 Operating System: Linux Debian Sarge 3.1
 PHP Version:      5.2.1
 Assigned To:      wez
 New Comment:

And I really surprised this issue not fixed for more than 2 year.


Previous Comments:
------------------------------------------------------------------------

[2009-09-08 12:56:51] weblab dot solutions at gmail dot com

Try PHP 5.2.9 & 5.3.0 - get the same exception.

------------------------------------------------------------------------

[2009-08-26 16:36:34] seb117 at free dot fr

I don't understand why this bug does not solved ? It's very important,
and we don't use PDO properly with this bug.

------------------------------------------------------------------------

[2009-08-22 05:59:07] marcel dot esser at gmail dot com

Same problem on 5.2.6, Ubuntu Jaunty.

------------------------------------------------------------------------

[2009-06-16 17:49:09] tony at tonybibbs dot com

Same issue on 5.3.0RC2 using pretty much the same code in the initial
bug report.

------------------------------------------------------------------------

[2009-02-18 08:51:00] nduteil at freedev dot org

Hi,
Still not fixed in the 5.2.8 release. If PDOStatement::bindParam or
PDOStatement::bindValue is used to specified the parameter type (ie : 
PDO::PARAM_INT) everything works as expected. Not forcing the parameter
type to integer generates an error in Mysql.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/40740

-- 
Edit this bug report at http://bugs.php.net/?id=40740&edit=1

Reply via email to