Bug #41997 [Ver->Csd]: SP call yields additional empty result set

From: Date: Tue, 03 Sep 2019 11:34:28 +0000
Subject: Bug #41997 [Ver->Csd]: SP call yields additional empty result set
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-222538@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=41997&edit=1

 ID:                 41997
 Updated by:         cmb@php.net
 Reported by:        nitel_defect at yahoo dot com
 Summary:            SP call yields additional empty result set
-Status:             Verified
+Status:             Closed
 Type:               Bug
 Package:            PDO MySQL
 Operating System:   *
 PHP Version:        5.2.3
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

Automatic comment on behalf of cmbecker69@gmx.de
Revision: http://git.php.net/?p=php-src.git;a=commit;h=41a4379cb45419a376043ca5f8c5a2bca82cea7c
Log: Fix #41997: SP call yields additional empty result set


Previous Comments:
------------------------------------------------------------------------
[2019-08-06 12:58:24] cmb@php.net

The following pull request has been associated:

Patch Name: Fix #41997: SP call yields additional empty result set
On GitHub:  https://github.com/php/php-src/pull/4496
Patch:      https://github.com/php/php-src/pull/4496.patch

------------------------------------------------------------------------
[2019-08-06 12:57:58] cmb@php.net

> not sure about libmysqlclient yet

Behaves the same.

------------------------------------------------------------------------
[2019-08-05 07:58:19] cmb@php.net

The originally reported issue has been basically resolved, but the
fix for bug #40935 broke the test case as reported by stas@ above.
The relevant behavior of calling stored procedures is described in
the documentation[1]:

| The final result from the procedure is a status result that
| includes no result set. The status indicates whether the procedure
| succeeded or an error occurred.

This is not properly handled by mysqlnd, though (not sure about
libmysqlclient yet), which simply proceeds to this status result
when ::nextRowset() is called, but then errors because the actual
result set is missing.

[1] <https://dev.mysql.com/doc/refman/8.0/en/c-api-multiple-queries.html>

------------------------------------------------------------------------
[2019-08-05 07:40:05] cmb@php.net

Related To: Bug #39858

------------------------------------------------------------------------
[2015-07-10 12:41:58] spam2 at rhsoft dot net

Related To: Bug #70039

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


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

    https://bugs.php.net/bug.php?id=41997


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


Thread (21 messages)

« previous php.bugs (#222538) next »