note 80426 added to function.mysqli-stmt-prepare
| From: | lukaszNOSPAMPLEASE at epas dot pl | Date: | Tue, 15 Jan 2008 15:15:04 +0000 |
| Subject: | note 80426 added to function.mysqli-stmt-prepare | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-135118@lists.php.net to get a copy of this message | ||
i've got some bad news for you guys if you haven't found out already.
the trick with mysqli_next_result() only prevents having the connection dropped after a stored
procedure call.
apparently you can bind parameters for a prepared stored procedure call, but you'll get messed
up records from mysqli_stmt_fetch() after mysqli_stmt_bind_result(), at least when the stored
procedure itself contains a prepared statement.
a way to avoid data corruption could be specifying the CLIENT_MULTI_STATEMENTS flag in
mysqli_real_connect(), if it wasn't disabled entirely (for security reasons, as they say).
another option is to use mysqli_multi_query(), but then you can't bind at all.
----
Server IP: 209.41.74.194
Probable Submitter: 83.22.106.199
----
Manual Page -- http://www.php.net/manual/en/function.mysqli-stmt-prepare.php
Edit -- https://master.php.net/note/edit/80426
Del: integrated -- https://master.php.net/note/delete/80426/integrated
Del: useless -- https://master.php.net/note/delete/80426/useless
Del: bad code -- https://master.php.net/note/delete/80426/bad+code
Del: spam -- https://master.php.net/note/delete/80426/spam
Del: non-english -- https://master.php.net/note/delete/80426/non-english
Del: in docs -- https://master.php.net/note/delete/80426/in+docs
Del: other reasons-- https://master.php.net/note/delete/80426
Reject -- https://master.php.net/note/reject/80426
Search -- https://master.php.net/manage/user-notes.php