SQL Import Error - Somewhat Urgent

[DrByte]

That error indicates that you've exported from a different version of MySQL than you're trying to import into, and the layout of the export data isn't fully compatible.

[DieuxSoldat_04]

Is there a method where I can make it compatible or maybe change an export setting?

- Jason

[DrByte]

Is there a method where I can make it compatible or maybe change an export setting?

I suppose that depends on the tools you're using to do your export. Do they give you some sort of compatibility options that match the version of MySQL you're trying to import into?

[DieuxSoldat_04]

The Host I am exporting with has a Backup Wizard and phpMyAdmin. I suppose phpMyAdmin would allow me to specify the settings, but I don't even know what I am suppose to change.

On one of the hosts I'm not even certain what version of MySQL it is. Their phpMyAdmin is different from most servers and when I create the Database it just lets me select 4.0 or 5.0.

The Old Database that I am exporting from uses MySQL client version: 4.1.22 and I did a phpinfocheck on the New Database I am importing too and it says Client API version 5.0.32. Not sure if that's the MySQL version.

As long as both has the phpMyAdmin tool, could someone walk me through the steps to make sure they are compatible?

Also, I was curious if it could be a collation problem?

Thanks!
- Jason

[DrByte]

It might be prudent to talk to the hosting company and confirm what version of MySQL is being used, especially if you plan to host your site there.

FAQ on using phpMyAdmin to make backups: https://www.zen-cart.com/tutorials/i...hp?article=103 There are compatibility options available, but should be used with caution. It's not uncommon to lose all auto-increment flags when switching between major MySQL versions, thus leaving your database in a confused state and unable to add new orders/customers/etc. It's especially ill-advised to ever go backwards, ie: from 5 to 4.

And, no, it's not a collation problem.

[DieuxSoldat_04]

Heya guys,

I contacted a college professor at my university. He advised the same thing but went ahead and edited for me. Turns out the Old Host said they were running 4.0 but was actually running 5.0. no idea how that could happen.

They tried to import to a version 5 SQL DB and it worked. I have to pick better hosts...

Thanks for your help DrByte!

- Jason