ID: 44597 Comment by: ant at specialops dot ath dot cx Reported By: kenaniah at gmail dot com Status: No Feedback Bug Type: PDO related Operating System: Red Hat 4.1.1 PHP Version: 5.2.6 New Comment:
I can still reproduce this on PHP 5.3.0 and PostgreSQL 8.4.1. Previous Comments: ------------------------------------------------------------------------ [2009-06-14 11:53:21] execut3 at gmail dot com The issue is still not fixed, I'm with PHP 5.2.6 on Ubuntu and postgresql 8.3. ERROR: invalid input syntax for type boolean: "" ------------------------------------------------------------------------ [2009-05-03 01:00:12] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2009-04-25 15:02:13] [email protected] Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://windows.php.net/snapshots/ ------------------------------------------------------------------------ [2009-02-04 03:57:28] kenaniah at gmail dot com This issue seems like it would be a very easy fix and can be reproduced without fail, regardless of server environment or PHP version. A fix would be greatly appreciated ------------------------------------------------------------------------ [2008-10-07 19:23:48] dac514 at hotmail dot com This is happening to me too, OS X and CentOS, PHP 5.2.6 I am converting a web application from MySql to PostgreSQL and i've run into a roadbloack that is forcing me to find every single boolean query and manually binding it instead of benefiting from execute() $input_parameters. PITA! I discovered the explanation to this "bug" here: http://ca.php.net/manual/en/pdostatement.execute.php#84990 As of 5.2.6 you still can't use PDOStatement->execute() $input_parameters to pass a boolean to PostgreSQL. To do that, you'll have to call bindParam() with explicit types for *each* parameter in the query. Pseudo example, where col5 is of type boolean (i.e. tinyint(1) in MySQL) $q = 'INSERT INTO table (col1, col2, col3, col4, col5, col6) VALUES (? , ?, ?, ?, ?, ?)'; $v = array('foo1', 'foo2', 'foo3', foo4', false, 'foo6'); $st = $db->prepare($q); $st->execute($v); PostgreSQL complains and the script dies. Leaving me in the cold and I have to rewrite the code, which becomes excessively painful when the queries are dynamically generated. PostgreSQL workaround, boooooo! $q = 'INSERT INTO table (col1, col2, col3, col4, col5, col6) VALUES (? , ?, ?, ?, ?, ?)'; $v = array('foo1', 'foo2', 'foo3', foo4', false, 'foo6'); $st = $db->prepare($q); $st->bindParam(1, $v[0]], PDO::PARAM_STR); $st->bindParam(2, $v[1]], PDO::PARAM_STR); $st->bindParam(3, $v[2]], PDO::PARAM_STR); $st->bindParam(4, $v[3]], PDO::PARAM_STR); $st->bindParam(5, $v[4]], PDO::PARAM_BOOL); $st->bindParam(6, $v[5]], PDO::PARAM_STR); $st->execute(); Can we get a fix for this soon? ------------------------------------------------------------------------ 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/44597 -- Edit this bug report at http://bugs.php.net/?id=44597&edit=1
