Zen Cart Logo
Forums / Upgrading from 1.3.x to 1.3.9 / database upgrade issue to version to 1.3.9e

database upgrade issue to version to 1.3.9e

Locked

Views: 1,602

Results 1 to 6 of 6
This thread is locked. New replies are disabled.
29 Jul 2010, 8:03 AM
#1
neit avatar

neit

Zen Follower

Join Date:
Feb 2010
Posts:
140
Plugin Contributions:
0

database upgrade issue to version to 1.3.9e

I did a database upgrade today from 1.3.9b to 1.3.9e and got the following message back:

SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot insert configuration_key "SHOW_SPLIT_TAX_CHECKOUT" because it already exists
SKIPPED: Cannot add index idx_prod_id_orders_id_zen to table orders_products because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.
SKIPPED: Cannot add index idx_cust_id_orders_id_zen to table orders because it already exists.

It also came up with: Could not rename all tables more info...
I am using the prefix zen_ but left the rename prefix blank.

Are these likely to cause any issues

29 Jul 2010, 9:01 AM
#2
kenichi avatar

kenichi

Zen Follower

Join Date:
Oct 2008
Posts:
252
Plugin Contributions:
0

Re: database upgrade issue to version to 1.3.9e

Since it's still 1.3.9, all you're meant to do is change the files that are different from the changelogs in the /docs/ folder from the fileset.

29 Jul 2010, 10:31 AM
#3
neit avatar

neit

Zen Follower

Join Date:
Feb 2010
Posts:
140
Plugin Contributions:
0

Re: database upgrade issue to version to 1.3.9e

ok
I changed the files, but thought I would update the databas to latest version also.
so I can just ignore these.

29 Jul 2010, 5:03 PM
#4
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,513
Plugin Contributions:
176

Re: database upgrade issue to version to 1.3.9e

You can just ignore those.

You'll also note in the upgrade instructions specific to 1.3.9e that it says there's no need to do any database-upgrade step if you've already got a prior v1.3.9xx version installed.

1 Aug 2010, 1:50 AM
#5
jokes54321 avatar

jokes54321

New Zenner

Join Date:
Dec 2009
Posts:
4
Plugin Contributions:
0

Re: database upgrade issue to version to 1.3.9e

So even though the DB Patch level says 1.3.9c, we are good since nothing changed in the DB? Just needing this additional clarification.

Thank you,

Denny

1 Aug 2010, 5:25 AM
#6
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,513
Plugin Contributions:
176

Re: database upgrade issue to version to 1.3.9e

Correct.