Bug #53483 [Opn]: using mysqli_stmt::send_long_data() makes execute() fail
| From: | andrey@php.net | Date: | Mon, 20 Dec 2010 15:50:59 +0000 |
| Subject: | Bug #53483 [Opn]: using mysqli_stmt::send_long_data() makes execute() fail | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-157144@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=53483&edit=1
ID: 53483
Updated by: andrey@php.net
Reported by: squarious at gmail dot com
Summary: using mysqli_stmt::send_long_data() makes execute()
fail
Status: Open
Type: Bug
Package: MySQLi related
Operating System: linux
PHP Version: 5.3.3
Block user comment: N
Private report: N
New Comment:
libmysql + MySQL 5.1.55
andrey@poohie:~/PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
mysqlnd + MySQL 5.1.55
andrey@poohie:~/PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
Previous Comments:
------------------------------------------------------------------------
[2010-12-20 16:02:05] andrey@php.net
libmysql + MySQL 5.0.90
andrey@poohie:~PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
libmysql + MySQL 5.5.8
andrey@poohie:~/PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
------------------------------------------------------------------------
[2010-12-20 15:55:06] andrey@php.net
mysqlnd with MySQL 5.0.90
andrey@poohie:~/PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
Error executing prepared statement. Got a packet bigger than
'max_allowed_packet' bytes
------------------------------------------------------------------------
[2010-12-20 15:10:31] andrey@php.net
with mysqlnd and MySQL 5.5.8 GA
andrey@poohie:~/PHP_5_3$ ./php a.php
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
Seems there was a problem in 5.5.5
------------------------------------------------------------------------
[2010-12-08 16:24:53] andrey@php.net
Looks a problem because of this MySQL Server bug
http://bugs.mysql.com/bug.php?id=26824
After trying the script with 5.3.4-dev , libmysql from Ubuntu 9.10 and
mysqlnd, and two different MySQL versions 5.1.51 and 5.5.5-m3.
MySQL 5.1
libmysql :
OK: Executed prepared statement with blob less than max_allowed_packet.
OK: Executed prepared statement with blob bigger than
max_allowed_packet, sent at chunks.
myslqnd:
OK: Executed prepared statement with blob less than max_allowed_packet.
and then few errors because of Packet out of order - an error packet
interleaving (see the MySQL bug description for more information)
MySQL 5.5
libmysql :
OK: Executed prepared statement with blob less than max_allowed_packet.
Error executing prepared statement. Incorrect arguments to
mysqld_stmt_execute
mysqlnd:
OK: Executed prepared statement with blob less than max_allowed_packet.
Error executing prepared statement. Incorrect arguments to
mysqld_stmt_execute
This needs more investigation with wireshark, something changed in the
server but in any case there was a problem. Haven't checked with MySQL
5.0, as I don't have one handy.
------------------------------------------------------------------------
[2010-12-08 15:49:40] jbreton at kronostechnologies dot com
I am experiencing the same problem, but I'm starting to think it is
related to
MySQL.
I'm also using php5.3.3 and mysql5.1.49, but colleague is using php5.3.3
and
mysql5.1.41 and your test passes without any problem.
------------------------------------------------------------------------
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/bug.php?id=53483
--
Edit this bug report at http://bugs.php.net/bug.php?id=53483&edit=1