php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

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
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: corinl at gmx dot de
New email:
PHP Version: OS:

 

 [2007-05-15 16:19 UTC] 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-12-20 14:20 UTC] jani@php.net
-Package: Feature/Change Request +Package: MySQLi related
 [2011-01-06 14:46 UTC] uw@php.net
-Assigned To: georg +Assigned To: mysql
 [2011-01-06 14:46 UTC] 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.
 [2011-01-24 10:22 UTC] uw@php.net
-Status: Assigned +Status: Wont fix
 [2011-01-24 10:22 UTC] uw@php.net 
Can be handled in user space.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 13:01:31 2024 UTC