Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.5.0b4

Bug #6887 tableInfo() bugged
Submitted: 2006-02-22 14:17 UTC
From: bate Assigned: lsmith
Status: Closed Package: MDB2_Driver_mysqli (version 1.0.0)
PHP Version: Irrelevant OS: WinXP
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 44 - 9 = ?

 
 [2006-02-22 14:17 UTC] bate (Marco Kaiser)
Description: ------------ mysqli_fetch_field returns wrong informations the attached bugfix should fix this tmp. Index: MDB2/MDB2/Driver/Reverse/mysqli.php =================================================================== RCS file: /repository/pear/MDB2/MDB2/Driver/Reverse/mysqli.php,v retrieving revision 1.29 diff -u -r1.29 mysqli.php --- MDB2/MDB2/Driver/Reverse/mysqli.php 13 Feb 2006 07:34:11 -0000 1.29 +++ MDB2/MDB2/Driver/Reverse/mysqli.php 22 Feb 2006 14:11:56 -0000 @@ -421,7 +421,7 @@ 'type' => isset($this->types[$tmp->type]) ? $this->types[$tmp->type] : 'unknown', - 'length' => $tmp->max_length, + 'length' => ($tmp->max_length < $tmp->length) ? $tmp->length : $tmp->max_length, 'flags' => $flags, ); $mdb2type_info = $db->datatype->mapNativeDatatype($res[$i]);

Comments

 [2006-02-26 18:02 UTC] lsmith
since this seems to be a work around a mysqli bug it would be important to get this bug filed on bugs.php.net, so that I can comment the change accordingly inside the mysqli driver.
 [2006-03-01 22:10 UTC] lsmith
Seems to be the same issue as http://pear.php.net/bugs/bug.php?id=5680
 [2006-03-01 22:56 UTC] lsmith
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.