Upgrade error 1.3.7->1.3.8a

[quentinjs]

1. It thinks I need to do an upgrade from 1.2.7->1.2.8 as well as from 1.3.7->1.3.8 And during the 1.3.8 upgrade I get this error.

Thanks !!!

1364 Field 'query_keys_list' doesn't have a default value
in:
[INSERT INTO query_builder (query_category, query_name, query_description , query_string) VALUES ('email,newsletters', 'Customers who have never completed a purchase', 'For sending newsletter to all customers who registered but have never completed a purchase', 'SELECT DISTINCT c.customers_email_address as customers_email_address, c.customers_lastname as customers_lastname, c.customers_firstname as customers_firstname FROM TABLE_CUSTOMERS c LEFT JOIN TABLE_ORDERS o ON c.customers_id=o.customers_id WHERE o.date_purchased IS NULL');]

[DrByte]

1. It thinks I need to do an upgrade from 1.2.7->1.2.8 as well as from 1.3.7->1.3.8

Sorry, I'm not sure I understand you.
There is no such thing as v1.2.8

[stevefriedman71]

Hi you gods of zen...

I have a small issue with the database update... i did merge everything successfulley data wise and then - as i clicked "update database from 1.3.7.1 to 1.3.8 in the install i received these errors:

SKIPPED: Cannot ADD column module_name because it already exists.
SKIPPED: Cannot ADD column module_mode because it already exists.
SKIPPED: Cannot CHANGE column zen_order_id because it does not exist.
SKIPPED: Cannot ALTER or INSERT/REPLACE into table linkpoint_api because it does not exist. CHECK PREFIXES!


so... i take that the first 2 are ok but i'm worried about the last 2 errors...

[DrByte]

Those "warnings" are informational, and suggest that some of the steps in the upgrade had already been done previously.
Thus, you should be safe to proceed.

Also note that the last warning is specifically listed as "okay" in the 1.3.8 announcement

[quentinjs]

So lets start this again.. I go in, say upgrade from 1.3.7. to 1.3.8 and get this error message...

1364 Field 'query_keys_list' doesn't have a default value
in:
[INSERT INTO query_builder (query_category, query_name, query_description , query_string) VALUES ('email,newsletters', 'Customers who have never completed a purchase', 'For sending newsletter to all customers who registered but have never completed a purchase', 'SELECT DISTINCT c.customers_email_address as customers_email_address, c.customers_lastname as customers_lastname, c.customers_firstname as customers_firstname FROM TABLE_CUSTOMERS c LEFT JOIN TABLE_ORDERS o ON c.customers_id=o.customers_id WHERE o.date_purchased IS NULL');]


thoughts?

[DrByte]

That error appears because that step has already been done once.

Follow the steps in this thread (which I found by searching for "Customers who have never completed") to delete that entry so you can start over again.
http://www.zen-cart.com/forum/showth...ever+completed


EDIT: Oops: I misread the error message, and recommended the wrong solution.

[quentinjs]

Thanks! That should I hope help a lot.

[quentinjs]

Okay it didn't help, which I think is due to the database being PHP5 / MySQL5. Any more thoughts?

# MySQL Version = 5.0.37
# PHP Version = 5.2.1

Actually I don't think the record is there. I know from past experiences with upgrades that if an insert is missing a field in the list then it wants a default value. Now part of the error message mentioned:

1364 Field 'query_keys_list' doesn't have a default value

So I wonder what the default value should be?

[DrByte]

Try running this to set the query_keys_list field to its correct format:

ALTER TABLE query_builder CHANGE COLUMN query_keys_list query_keys_list TEXT NOT NULL;

It comes from an upgrade step in the upgrade to 1.3.0.2 and 1.3.5 where that field was changed. Perhaps yours didn't get that step done properly for some reason.

[DrByte]

Actually I don't think the record is there. I know from past experiences with upgrades that if an insert is missing a field in the list then it wants a default value. Now part of the error message mentioned:

1364 Field 'query_keys_list' doesn't have a default value

So I wonder what the default value should be?

You're correct; however, a field of type "TEXT" never gets a default value. Thus, your table must have the old structure which used varchar ... way back in 1.2.something.

BLOB and TEXT columns cannot have DEFAULT values.