Fed up with phpMyAdmin errors #12848

Closed
RichardNg opened this Issue Dec 22, 2016 · 7 comments

Projects

None yet

3 participants

@RichardNg
RichardNg commented Dec 22, 2016 edited

Hello, phpMyAdmin drives me bunker! I just installed the latest 4.6.5.2. When I want to delete a row from a table, I keep getting this

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 1.

when I click on the Copy, I get this SQL query: DocumentationEdit Edit
SELECT * FROM whateverDB.whateverTable WHERE ;
MySQL said: Documentation

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

And when I click on Edit I get this
SQL query: DocumentationEdit Edit

SELECT * FROM whateverDB.whateverTable WHERE ;
MySQL said: Documentation

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

Whatda hell is wrong with phpMyAdmin? Where does phpMyAdmin gets the MySQL statements from and how do I fit it? Thank you.

@ibennetch
Contributor
@RichardNg
@nijel
Member
nijel commented Dec 23, 2016

Most likely you have the MySQL server configured with lower_case_table_names=2, it behaves a bit oddly in this case and this has been fixed for next phpMyAdmin release, see #11816

@nijel nijel closed this Dec 23, 2016
@nijel nijel self-assigned this Dec 23, 2016
@nijel nijel added this to the 4.6.6 milestone Dec 23, 2016
@RichardNg
@ibennetch
Contributor

Personally, I think changing the MySQL configuration is the proper solution, but it probably means dumping and recreating your databases and tables (or, probably although not tested, at least renaming them all to lower case names before changing the configuration). So I don't "recommend" doing it, I just think that's the ideal solution (based on the MySQL manual).

Anyway, what I would do if I were you is to apply the patch I linked to from the other thread (from Terminal, I put the .patch file one directory level up from phpMyAdmin and used patch -p1 < ../715bdf3.patch to apply the patch; it failed a portion of the ChangeLog but that doesn't affect the functionality). I think that will clear things up without causing any other problems.

The best solution will be once 4.7.0 is out.

@RichardNg
@nijel
Member
nijel commented Jan 2, 2017

As you can see from the milestone set on this issue, 4.6.6 will fix it.

fed_up_with_phpmyadmin_errors_ issue 12848_ phpmyadmin_phpmyadmin-_2017-01-02_16 39 02

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment