On Sat, 10 Aug 2002, Rabus wrote:
----- Original Message ----- From: "Robin Johnson" robbat2@fermi.orbis-terrarum.net
I've been looking at the bug list, trying to see what remaining stuff is really important.
The only one I see is: #590055 (2.3.0-rc4) Empty Corrupts Tables
This is a MySQL 4 bug, not a phpMyAdmin one. Furthermore, I cannot reproduce it on my machine. I'm not sure if we should work around it because MySQL 4.0.2 is still an alpha release. But this imho is no show stopper.
Since the command causing problems is the TRUNCATE TABLE, which empties out the entire table. Running OPTIMIZE afterwards should be really quick as the table is empty, therefore there should be no performance hit to running it. Or if you really want to avoid running it, could you just put in a specical case for it? if (PMA_MYSQL_INT_VERSION == 40002) ...
I think we should have even this workaround fix in place.