#4682 4.3.3 & 4.3.4 Import sql created by mysqldump fails on foreign keys

[Gary]

Server type: MySQL
Server version: 5.6.21 - MySQL Community Server (GPL)
Protocol version: 10
User: root@localhost
Server charset: UTF-8 Unicode (utf8)
OS X 10.10.1

Created .sql export using mysqldump
Prior to phpmyadmin 4.3.3 (not sure which) the import .sql would work, no issues.
phpmyadmin 4.2.13.1 which I'm using now does import .sql with no issues.
Versions 4.3.3 and 4.3.4 both fail the import .sql the same way when it hits a foreign key
When creating the export .sql in phpmyadmin, any of the above version work on the import but these export files are much larger than mysqldump which I use in a command line script

If you need any more info please contact me - Gary

[Madhura Jayaratne]

Can you attach a small sample sql files exported with mysqldump that fails.

[Gary]

In phpmyadmin create database, select it and import the attached which has 3 small tables with foreign keys. Will load correctly in phpmyadmin 4.2.13.1 but fail in 4.3.3 and 4.3.4

testx.sql created with mysqldump Ver 10.13 Distrib 5.6.21, for osx10.8 (x86_64)

[Hugues Peccatte]

For information, I think this is clearly linked to my fix for #4645 (see commit 2dcb1c9b0a9c6603a3bb39fb49f568a2c8d9b5cd).
I'm currently waiting for an answer into this other ticket to see what to do.
Sorry for the wait.

[Hugues Peccatte]

I sent a PR for this ticket: https://github.com/phpmyadmin/phpmyadmin/pull/1446

[Marc Delisle]

Merged, thanks.