|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #41402 no safe way to retrieve warnings
Submitted: 2007-05-15 16:19 UTC Modified: 2011-01-24 10:22 UTC
From: corinl at gmx dot de Assigned: mysql (profile)
Status: Wont fix Package: MySQLi related
PHP Version: 5.2.2 OS: debian 686
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2007-05-15 16:19 UTC] corinl at gmx dot de
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.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2010-12-20 14:20 UTC]
-Package: Feature/Change Request +Package: MySQLi related
 [2011-01-06 14:46 UTC]
-Assigned To: georg +Assigned To: mysql
 [2011-01-06 14:46 UTC]
Not needed, there is 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.
 [2011-01-24 10:22 UTC]
-Status: Assigned +Status: Wont fix
 [2011-01-24 10:22 UTC]
Can be handled in user space.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Mon Dec 06 15:03:34 2021 UTC