Req #41402 [Asn->Wfx]: no safe way to retrieve warnings
| From: | uw@php.net | Date: | Mon, 24 Jan 2011 09:22:40 +0000 |
| Subject: | Req #41402 [Asn->Wfx]: no safe way to retrieve warnings | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-158134@lists.php.net to get a copy of this message | ||
Edit report at http://bugs.php.net/bug.php?id=41402&edit=1
ID: 41402
Updated by: uw@php.net
Reported by: corinl at gmx dot de
Summary: no safe way to retrieve warnings
-Status: Assigned
+Status: Wont fix
Type: Feature/Change Request
Package: MySQLi related
Operating System: debian 686
PHP Version: 5.2.2
Assigned To: mysql
Block user comment: N
Private report: N
New Comment:
Can be handled in user space.
Previous Comments:
------------------------------------------------------------------------
[2011-01-06 14:46:35] uw@php.net
Not needed, there is
http://de3.php.net/manual/en/mysqli.warning-count.php
to check if
warnings exist and if they do, you can fetch them in user space and
preserve all mysqli properties you are interested in.
------------------------------------------------------------------------
[2007-05-15 16:19:12] corinl at gmx dot de
Description:
------------
using $m->query('SHOW WARNINGS') changes $m->affected_rows, so it cannot
be used when extending the class. also, affected_rows is write protected
so it cannot be saved and restored after fetching the warnings.
$m->get_warnings() does not seem to work yet.
Reproduce code:
---------------
see above
Expected result:
----------------
please make $m->query('SHOW WARNINGS') not to change change
$m->affected_rows. if this is not desired, please make get_warnings()
functional.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=41402&edit=1