#35428 [Bgs]: crash when using mysqli with MySQL 5.0.16
| From: | tony2001@php.net | Date: | Thu, 01 Dec 2005 09:38:00 +0000 |
| Subject: | #35428 [Bgs]: crash when using mysqli with MySQL 5.0.16 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-89554@lists.php.net to get a copy of this message | ||
ID: 35428
Updated by: tony2001@php.net
Reported By: marcing at smlw dot pl
Status: Bogus
Bug Type: MySQLi related
Operating System: WinXP SP2
PHP Version: 5CVS-2005-11-28 (snap)
Assigned To: georg
New Comment:
MySQL client bugs should be reported in another place and they are
obviously not PHP bugs.
Previous Comments:
------------------------------------------------------------------------
[2005-12-01 10:27:51] marcing at smlw dot pl
Right, its better to pretend there is no problem, just stick a label
"bogus" and forget.
Why did a have a feeling that u wont care anyway?
In the bug - http://bugs.php.net/bug.php?id=35388, georg might
have
given the reason and possible solution for this problem (my client
version is 4.1.7 too).
That could explain why u cant reprocude it.
But its so hard to think...i know...
Its time for u to paste this "Please try using this CVS snapshot:"
text, right?
------------------------------------------------------------------------
[2005-11-30 15:56:33] iliaa@php.net
Can't replicate on latest cvs.
------------------------------------------------------------------------
[2005-11-30 15:49:08] marcing at smlw dot pl
The size is unchanged, the bug still exists, so where is the
difference?
------------------------------------------------------------------------
[2005-11-30 14:49:26] tony2001@php.net
Why do you think it's unchanged?
The url is the same, while file is regenerated every time.
------------------------------------------------------------------------
[2005-11-30 14:47:43] sniper@php.net
No, nothing. Don't bother, it's fixed. And reported by dozen other
people too..
------------------------------------------------------------------------
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
http://bugs.php.net/35428
--
Edit this bug report at http://bugs.php.net/?id=35428&edit=1