Your database appears to need patching to a higher level. See Tools->Server Informati

[pocketpenny]

Oh, err... I just did what this thread says:

http://www.zen-cart.com/forum/showth...abase+patching

Yay!

[honrheart]

Trying to upgrade my database and when I click the upgrade database I get the following message:

1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8'
in:
[CREATE TABLE zen_counter_history_clean as SELECT * FROM zen_counter_history WHERE 1 GROUP BY startdate COLLATE latin1_general_ci;]

Someone said in another post I need to edit the sql update but how do I do that exactly?

[diane42]

Hello,

I'm afraid I need help with this too. I have read loads of posts and docs, but I just need to clarify the process.

I have an old zenCart installation version 1.3.8a

I have moved it to a new version 1.3.9d

it all looks fine except for the database patch message.

Do I need to do the following?

1 update the old version to 1.3.9f then export the database

2 update or even delete and do a new manual install of 1.3.8f on the new server

3 import the updated database to the new 1.3.9f installation

It all seems a bit scary and i don't want to break the old installation, please help
thanks

[castlino]

Hey guys i think most of you who had database problems have upgraded to the new version using initially your old database. You should use a new/fresh database if you do full upgrade, then just restore the old database by overwriting the new one.

Anyway its not yet too late as long as you have a copy of your unaltered old database.

Here's what you might do:
1. Create backup of the old database
[FONT="Courier New"]mysqldump -u [user] -p OldDbName > OldDbBackup.sql[/FONT]
(Then enter [user] password if prompted..)
2. Restore it to the new one
[FONT="Courier New"]mysql -u [user] -p OldDbBackup.sql > NewDbName[/FONT]

[DrByte]

castlino,
1. Most people have no access to command-line, so cannot do what you're suggesting ... and most would have no clue what you're even suggesting, and shouldn't even try.
And those who *do* know what you're talking about have probably already done their upgrade without difficulty.

2. There's nothing wrong with upgrading the original database directly (after first doing a test upgrade in a separate database first to make sure everything works fine there before touching the live site).

3. What you're talking about seems to be very narrow-scoped in its context and doesn't take into account the big picture of what "most of you who had database problems" are all experiencing.

Please excuse me if I sound rude or offensive: I don't mean to be.
I just think your post would be confusing to most people, and that if they find it confusing then they should ignore it.