Database upgrade 1.3.0.1 to 1.3.0.2 - some table skipped?

**donnyw** · 20 Jul 2006, 08:46 AM

I just upgraded my zencart and database from v1.3.0.1 using v1.3.0.2 changed files set only, already put new files and went to zc_install and click 'upgrade database'.

It works, but some tables skipped as below:

SKIPPED: Cannot insert configuration_key "UPLOAD_PREFIX" because it already exists
SKIPPED: Cannot insert configuration_key "TEXT_PREFIX" because it already exists
SKIPPED: Cannot insert configuration_key "MAX_META_TAG_DESCRIPTION_LENGTH" because it already exists
SKIPPED: Cannot insert configuration_key "MAX_META_TAG_DESCRIPTION_LENGTH" because it already exists
SKIPPED: Cannot insert configuration_key "MAX_META_TAG_DESCRIPTION_LENGTH" because it already exists

Should I manually replace the tables, or is there any method to avoid this little problem?

**dbltoe** · 20 Jul 2006, 05:22 PM

What the system is telling you is that you already created the tables in a previous upgrade.

You can generally disregard

SKIPPED: Cannot insert various statements seen here because it already exists

because the system is telling you it wanted to create it but it was already there.

**donnyw** · 21 Jul 2006, 01:36 AM

Thanks.. I understand your point.

Does it mean I already have the latest database's tables for 1.3.0.2?
Actually I tested the upgrade not on the live site, still doing testing in my PC.

I have a thought that those skipped tables still had previous 1.3.0.1 entries in them... since MetaTag was one of the bug issue found in 1.3.0.1.. I'm afraid that the bug not yet resolved.

Anyhow I will check and compare both version entries and see whether they are the same or not.

**dbltoe** · 21 Jul 2006, 07:07 AM

The Meta Tag problems were in code, not data.

Besides, had there been a problem in the database, the SQL would have overwritten or deleted/replaced the offending item.

The devs get a BIG

for that one and maybe a little

too.

OR.... Just throw money!

**donnyw** · 14 Aug 2006, 09:46 AM

Thanks dbltoe

Yesterday I tried to upgrade my site using the same way and getting that warning again.

However I assume that I wont have problem because of that, since it is not essential.

I just curious why no other people has the same problem with me despite I follow normal upgrading procedure :) ... maybe the mistake on my side.

**DrByte** · 14 Aug 2006, 10:19 AM

Several others have encountered the same warning messages for the same reason you did. The message is indicating that some upgrade steps were not necessary for "your" database.