#36812 [Asn->Csd]: bind NULL variables generates warning

ID: 36812 Updated by: iliaa@php.net Reported By: ce at netage dot bg -Status: Assigned +Status: Closed Bug Type: PostgreSQL related Operating System: linux PHP Version: 5.1.3RC1 Assigned To: helly New Comment: This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2006-11-11 14:16:51] dave@php.net This happens because pg_execute() modifies the array values, so $temp1 gets passed a NULL initially, then $temp1 is converted to a string which is why the second time it is passed it fails to execute. This can be demonstrated by doing var_dump($temp1); before and after the pg_execute() statement. I don't claim to know PHP internals, but perhaps the fact that it uses convert_to_string() instead of convert_to_string_ex() is the cause? ------------------------------------------------------------------------ [2006-09-26 22:30:01] tony2001@php.net Assigned to the maintainer. ------------------------------------------------------------------------ [2006-03-23 09:58:44] ce at netage dot bg check the workarround and see how an array of $param_list = array(null, null, null); does NOT generate any error, actually working as expected (so the problem is not at the integer type of the column, because it has the right to be NULL) ------------------------------------------------------------------------ [2006-03-22 18:19:30] iliaa@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php You declare the parameter is being of type INT and then put NULL into it. Is it any wonder PostgreSQL generates an error? ------------------------------------------------------------------------ [2006-03-21 12:38:16] ce at netage dot bg Description: ------------ when binding explicit null value there is no problem (see the workarround), but, when the null value is from variable there is a problem (the example is stupid, but is the simplest one representing the problem) Reproduce code: --------------- CREATE TABLE nullproblem (i integer); <? $conn = pg_connect('dbname=test'); $temp1 = null; $param_list = array($temp1, $temp1, $temp1, ); /******************* workarround: $param_list = array(is_null($temp1)?null:$temp1, is_null($temp1)?null:$temp1, is_null($temp1)?null:$temp1, ); ****************/ pg_prepare($conn, 'test', 'INSERT INTO nullproblem VALUES (case when $2::int IS NULL then $3::int else $1::int end)'); pg_execute($conn, 'test', $param_list); ?> Expected result: ---------------- nothing special Actual result: -------------- Warning: pg_execute(): Query failed: ERROR: invalid input syntax for integer: "" in test.php on line 10 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=36812&edit=1