#39858 [Com]: Lost connection to MySQL server during query by a repeated call stored proced

From: Date: Sat, 05 Apr 2008 16:56:26 +0000
Subject: #39858 [Com]: Lost connection to MySQL server during query by a repeated call stored proced
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-123988@lists.php.net to get a copy of this message 
 ID:               39858
 Comment by:       php at pofik dot com
 Reported By:      develar at gmail dot com
 Status:           Assigned
 Bug Type:         PDO related
 Operating System: Windows XP SP2
 PHP Version:      5.2.0
 Assigned To:      wez
 New Comment:

Hi there - so is there a proper fix for this by now? I just started
using stored procedures more extensively and I am now hit by this bug
all the time (Windows XP SP2, MySQL 5.0.51a, PHP 5.2.1)! Apparently this
bug is a known problem since at least October 2005 (Bug #5827), so I'd
think this should be long fixed?? However, I cannot locate any
information on a proper fix except for a bunch of makeshift workarounds
(using ODBC, abandoning the connection on HY000 etc.), and tons of
people complaining about it not being fixed. 

Considering how long this bug is known and open, it would help if
someone could post some update. This issue is really really annoying.

Thanks!


Previous Comments:
------------------------------------------------------------------------

[2008-02-07 12:57:17] kraus at phoenix-medien dot de

This PDO bug makes it impossible to install Magento on Windows
platforms. See
http://www.magentocommerce.com/wiki/general/installing_on_windows_with_xampp_and_wamp
for further information.

------------------------------------------------------------------------

[2007-12-17 08:33:59] poon dot fung at gmail dot com

Same problem presist on Windows XP with PHP v5.2.5. Again, here is the
error message. When a query is executed after calling a stored
procedure.

code: HY000, msg: Cannot execute queries while other unbuffered queries
are active.  Consider using PDOStatement::fetchAll().  Alternatively, if
your code is only ever going to run against mysql, you may enable query
buffering by setting the PDO::MYSQL_ATTR_USE_BUFFERED_QUERY attribute.

------------------------------------------------------------------------

[2007-09-12 15:20:56] timo at hhesse dot de

Well, months pass by and nothing happens... ;-(

------------------------------------------------------------------------

[2007-07-14 20:12:41] nitel_defect at yahoo dot com

What's the status of this bug?
I mean the part about any query ran after a fetchAll from a stored
procedure call, saying that there are still unfetched results. And that
happens even with a nextRowset call :)
The bug still exists in the last library from snaps, on Windows.

------------------------------------------------------------------------

[2007-07-10 13:38:46] matt dot keeble at gmail dot com

As an update to this, I'm not sure that this is a bug in PHP at all - I
believe it's a bug with MySQL. Have stumbled across this bug report
today after receiving MySQL lost connections from the MySQL command
line, and from Navicat Terminal - in both cases there was no PHP
involved at all, just an SP that calls a function in a loop which
subsequently calls another function. The SP returns the first row, but
then dies with the error message and goes into an irretrievable loop (in
Navicat).

Don't know if this will help, but thought I would share...

------------------------------------------------------------------------

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/39858

-- 
Edit this bug report at http://bugs.php.net/?id=39858&edit=1

Thread (44 messages)

« previous php.bugs (#123988) next »