|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2018-07-06 11:00 UTC] dan dot ridgway at proximity dot co dot uk
-Operating System: V7R3
+Operating System: IBMi V7R3
[2018-07-06 11:00 UTC] dan dot ridgway at proximity dot co dot uk
[2018-07-06 11:58 UTC] cmb@php.net
-Status: Open
+Status: Assigned
-Assigned To:
+Assigned To: vnkbabu
[2018-07-06 11:58 UTC] cmb@php.net
[2018-07-18 12:34 UTC] shlomo dot v at zend dot com
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Oct 28 08:00:01 2025 UTC |
Description: ------------ If you try to bind a parameter of blank or empty in a UPPER(?) query it will try to allocate 1073741824 bytes no matter what field or file you are running the query on. Exmaple of query that is broken... SELECT ADDID, ADDNAME from ADDRESS where UPPER(ADDNAME) LIKE UPPER(?) ? is a empty string with no spaces. The above logs the following error on the function db2_execute($stmt)... PHP Fatal error: Allowed memory size of 786432000 bytes exhausted (tried to allocate 1073741824 bytes) Example of query that works... SELECT ADDID, ADDNAME from ADDRESS where UPPER(ADDNAME) LIKE UPPER('') Instead of binding the parameter using db2_bind_param you can include the value in the statement and it works fine. This bug only seems to happen on binding a parameter using db2_bind_param with an empty value that's then used in a UPPER function in the query.