Database backward compatibility?

[gaw]

I'm switching hosts (or trying to, at least).

The old host was using MySQL 5.0, the new host uses 4.0.27.

When importing the DB, I've got this error;

CREATE TABLE `address_book` (
`address_book_id` int( 11 ) NOT NULL AUTO_INCREMENT ,
`customers_id` int( 11 ) NOT NULL default '0',
`entry_gender` char( 1 ) NOT NULL default '',
`entry_company` varchar( 32 ) default NULL ,
`entry_firstname` varchar( 32 ) NOT NULL default '',
`entry_lastname` varchar( 32 ) NOT NULL default '',
`entry_street_address` varchar( 64 ) NOT NULL default '',
`entry_suburb` varchar( 32 ) default NULL ,
`entry_postcode` varchar( 10 ) NOT NULL default '',
`entry_city` varchar( 32 ) NOT NULL default '',
`entry_state` varchar( 32 ) default NULL ,
`entry_country_id` int( 11 ) NOT NULL default '0',
`entry_zone_id` int( 11 ) NOT NULL default '0',
PRIMARY KEY ( `address_book_id` ) ,
KEY `idx_address_book_customers_id_zen` ( `customers_id` )
) ENGINE = MYISAM DEFAULT CHARSET = latin1 AUTO_INCREMENT =153;

MySQL said: #1064 - You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT CHARSET=latin1 AUTO_INCREMENT=153' at line 17

Down here in Texas, a syntax is what the government charges for whiskey and cigars... what syntax modifications do I need to make here? Do I need to modify each individual table? Is there an easier way to make my database backward compatible to 4.027? Should I throw in the towel and ask my customers to just mail me a check?

[Ryk]

I'm no expert on MySql but I recall having had a similar problem in the past; I think if you remove DEFAULT CHARSET = latin1 it may work. Might not, but something to try until an expert gets here.

Note that your new host should be thinking about upgrading to MySql5 soon - if not, then I'd suspect that you may be moving to a server that's not kept up to date.

[kuroi]

I had that problem a while ago when trying to install a site in a client's hosted space.. I believe that we ended up having to remove all the ENGINE = MYISAM references (though it was a while ago and Ryk could be right, it might have been the DEFAULT CHARSET = latin1 references), several times, until the client was persuaded to move to a host using more up-to-date technologies.

In any case, I would question the wisdom of switching to a host using a version of MySQL that has already gone beyond the end of its official life.

I would also check whether this host has moved to PHP5. If not you are walking into a potential minefield as PHP4 has also now passed the end of its official life.

[Merlinpa1969]

kuroi,


that was php4 that went EOL not mysql.... LOL

bot I tend to think its comming soon

[kuroi]

Active support for MySQL 4.0 and 4.1 ended in 2006 (Sept and Dec respectively). There is limited support for some commercial customers only until the end of 2008 and 2009 respectively, and then only for bugs that affect security or are deemed to have severity level 1.

[Merlinpa1969]

I meant 4x in general

[gaw]

FYI, killing the DEFAULT CHARSET = latin1 reference did the trick.

My old host is hopelessly helpless, so I've got to get this ported over and running today, hence using the host w/ the outdated php/mysql. I just hope it doesn't break too badly when they upgrade.

New question:

I loaded the latest and greatest Z-cart, version 1.3.8a, which seems to have one table more than version 1.3.8 (which my data is in.)

Any idea what the extra table is, and what its structure is?

[Ajeh]

That new database is probably for the nocheck payment module ...

Best way to find out ... is to compare them using phpMyAdmin.