MySQL 5 injures phpMyAdmin

KirkM · Unread post by **KirkM** » Tue Jul 10, 2007 11:10 am

I have upgraded my Plesk 8.1.1 box to PHP 5 / MYSQL 5 and everything seems to work great except phpMyAdmin. It works, but there is a problem with copying tables. It appears that since phpMyAdmin is tied to Plesk and is still version 2.8.2.4 and the client version is 4.1.20, there is an issue with them playing nice with MYSQL 5. I have searched around for ways to upgrade the client and / or phpMyAdmin with no luck.

I worked quite a long time trying to modify phpMyAdmin's latest version, but it just won't work with Plesk.

Anybody have a fix for this or info on how to correctly update the client?

Thanks.

Troy McClure · Wed Jul 11, 2007 10:19 am

How are you copying the tables? I tried to duplicate this problem, but it seems to be ok with mine. I don't use phpMyAdmin. I did have a similar problem after the upgrade to MySQL5 which I fixed by upgrading some tables. You may find my posts in this thread helpful. http://atomicrocketturtle.com/forum/vie ... =mysql+php

KirkM · Unread post by **KirkM** » Wed Jul 11, 2007 1:10 pm

I am trying to use the "COPY TABLE" function in the OPERATIONS tab in phpMyAdmin.

You can see where it isn't putting a space into the SQL string so it misfires trying to create the table in the copy process. It has to do with the auto-increment being passed in the copy function since creating a new table works fine - it isn't trying to pass the next increment value in that process.

Yes, I read that post, along with dozens of others, but that is not my problem. PHP5 / MYSQL 5 work fine. It is phpMyAdmin within Plesk that is having the issue with the new version. The phpMyAdmin team just responded to me that it was a bug in phpMyAdmin working with MYSQL 5 that was fixed in a later version of phpMyAdmin than the one built into Plesk 8.1.1. The problem is I can't get a later version of phpMyAdmin to work with Plesk (INSIDE Plesk, not externally).

I'm crossing my fingers that 8.2 addresses this and that it comes out very soon.

KirkM · Unread post by **KirkM** » Wed Jul 11, 2007 3:03 pm

So 8.2 comes out right after I type my message above. SWSoft has done it again:

23. Upgrade of phpMyAdmin (Windows version only) – phpMyAdmin in Plesk for Windows has been updated.

26. Upgrade of clients MySQL (Windows version only) – MySQL has been upgraded to latest version.

WINDOWS VERSION ONLY?!?!?!?! WTF?!?!?!

Troy McClure · Unread post by **Troy McClure** » Wed Jul 11, 2007 4:23 pm

I'm not sure about that because I was able to copy tables with that function no problem. Added autoincrement and everything. Do you have a lot of tables to copy or something? Why don't you just fix the statement and run it yourself?

KirkM · Unread post by **KirkM** » Wed Jul 11, 2007 4:34 pm

Yes, I have to constantly copy tables with data for a number of my clients. I'm not a big fan of doing long workarounds for something that is supposed to work. I'd rather fix the problem so that it does what it is supposed to do. If Plesk had updated the client and phpMyAdmin in the Linux version of 8.2 as they should have since they claim support for MYSQL 5, then this wouldn't be an issue. It appears it DOESN'T really support MYSQL 5 completely since that build of phpMyAdmin is contained in their package.

SWSOFT is a real disappointment since I moved from Ensim over to Plesk.

Unread post by **scott** » Wed Jul 11, 2007 5:23 pm

Is anyone else able to reproduce this? I must be doing something wrong, Im not getting that on my system here. Similar environment, centos 4 that was upgraded to mysql 5.0.27 from my archive.

Which mysql5 are you using?

Troy McClure · Unread post by **Troy McClure** » Wed Jul 11, 2007 5:48 pm

I was actually able to reproduce this error. I have 2 production boxes which both have this problem and 1 test box that doesn't have this problem. Not sure what the difference is because they are all the same (CentOS 4.5, PSA 8.1.1).

KirkM · Unread post by **KirkM** » Wed Jul 11, 2007 8:07 pm

I have mysql 5.0.27 from your ART archive. I have 2 RHEL 4 boxes and they both do it.

When trying to reproduce the error, remember that it has to be a copy of an existing table with data in it. Creating a new table with phpMyAdmin works fine.

Highland · Unread post by **Highland** » Thu Jul 12, 2007 10:28 am

Not a solution but a workaround...

Try installing phpMyAdmin yourself. You can get the latest version with the bug fixed and use the default Plesk certificate to get SSL.

I tried this under Plesk 8.1.1 (phpMyAdmin 2.8.4.2, latest ART release of everything) and I got the same error but I tried it under a separate install (I work a lot in that DB) of phpMyAdmin 2.10.0.2 (not even the latest release) and it worked fine.

Bit surprised they didn't bump the Linux phpMyAdmin in 8.2 but they left a lot of promised Linux changes out as well.

Unread post by **scott** » Thu Jul 12, 2007 10:56 am

Too many OS's to support I think. As an example implementing PSA with postfix on RHEL or CentOS is easy. Doing that on freebsd, ubuntu, suse, osx, etc is hard, each one is exponentially increasing development time. That was one of the reasons I was so hot on dumping the other distros at plesk.