#19283 [Fbk->Csd]: phpMyAdmin doesn't work with 4.2.3
| From: | sniper@php.net | Date: | Wed, 09 Oct 2002 02:44:58 +0000 |
| Subject: | #19283 [Fbk->Csd]: phpMyAdmin doesn't work with 4.2.3 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-21874@lists.php.net to get a copy of this message | ||
ID: 19283
Updated by: sniper@php.net
Reported By: mimerker@solidcore.de
-Status: Feedback
+Status: Closed
Bug Type: MySQL related
Operating System: Suse Linux 7.2
PHP Version: 4.2.3
New Comment:
This bug has been fixed in CVS.
In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2002-09-21 15:23:53] stefb@wizzz.net
Sorry i didn't see there was a work around for that in
http://bugs.php.net/bug.php?id=19404
------------------------------------------------------------------------
[2002-09-21 15:18:28] stefb@wizzz.net
With phpMyAdmin 4.3.{0,1-rc1} when you edit a record or a table
property, or anything that has to do with data posted from an input
field that is to be translated into sql, the resulting string to be
sent to mysql has some truncated caracters and is of course wrong in
syntax for mysql. Apparently it doesn't happen with version prior to
php-4.2.2
I'm using RH 7.{0,3} apache-1.3.26 php-4.2.3 MySQL-3.23.5{1,2}
I've not seen the optimize tables bug (coz i don't optimize very often)
------------------------------------------------------------------------
[2002-09-18 17:06:00] iliaa@php.net
Can you please elaborate on '"optimize tables" kills the tables'?
There in fact there is a bug in MYSQL that was solved in upcomming
3.23.53 release, which could be what is causing the problem. The bug
description reads, 'Fixed a bug that OPTIMIZE of locked and modified
MyISAM table, reported table corruption'.
------------------------------------------------------------------------
[2002-09-18 10:20:01] mimerker@solidcore.de
i know some where it does, sorry :)
------------------------------------------------------------------------
[2002-09-18 10:19:04] mimerker@solidcore.de
suse 7.2 here. this bug does not affect all systems, but i know where
it does.
------------------------------------------------------------------------
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/19283
--
Edit this bug report at http://bugs.php.net/?id=19283&edit=1