Converting DB from OSC2.2 to OSCMAX2.2

[michael_s]

The workaround is this:

For any auto_increment field, remove the default value completely. It cannot be set for auto increment fields. Do that for all of the auto_increment fields and it will work. I just had to upgrade a db and had this exact error.

I simply did as I suggest and removed the default value from the query. For example:

 CREATE TABLE article_reviews( reviews_id int( 11 ) NOT NULL DEFAULT 0 COMMENT '' AUTO_INCREMENT

becomes:

 CREATE TABLE article_reviews( reviews_id int( 11 )  NOT NULL COMMENT '' AUTO_INCREMENT

Note that you will have to go through the entire sql query and remove all instances of this through the entire query for auto_increment fields

[tcshadow]

I'm still having trouble with this... it seems i can import the products and the categories but the 2 of them don't link up... the categories look empty but the products are showing in the what's new section.

[michael_s]

You are forgetting to import the 'products_to_categories' table. That is what maps the products to the correct categories.

[tcshadow]

aah ok I'll give that a go.

I was hoping to be able to copy it across in its entirety but it keeps throwing errors at me when I do that... doing a few tables at a time seems to work quite well.

[tcshadow]

1054 - Unknown column 'cd.categories_heading_title' in 'field list'

select cd.categories_name, cd.categories_heading_title, cd.categories_description, c.categories_image from categories c, categories_description cd where c.categories_id = '23' and cd.categories_id = '23' and cd.language_id = '1'

[TEP STOP]

What does that mean?

[tcshadow]

--
-- Database: `xxxxxx`
--
--
-- Dumping data for table `products`
--
INSERT INTO `products`
VALUES ( 63, 20, '51626A', '26.JPG', 44.5455, '2007-04-05 10:30:48', '2008-01-11 09:54:24', NULL , 0.08, 1, 1, 9, 0 ) ;

MySQL said:
#1136 - Column count doesn't match value count at row 1


I would like to shoot myself

[michael_s]

The above errors mean you are not really understanding what it is that you need to do to move old osC 2.2 data to osCMax.

You can't just import the data directly from an osC 2.2 database to osCMax. You need to convert the table structure of the old osC 2.2 database to match the osCMax structure first. Use mysqldiff to create the batch file to update the structure of the old osC 2.2 database (don't change the orginal db, only work on a copy to keep your original safe in case you mess up).

Once you have updated the structure of the old osC 2.2 datbase to match the osCMax database, then you can export the data to the osCMax database and you should not get the above errors anymore.

You need to do a bit more reading about mysql and how to manipulate tables, etc. There are a lot of tutorials out there floating around on google...

[tcshadow]

I thought i had already done the conversion using mysqldiff... I may have f-ed something up along the way... guess I'll go back to the beginning and try again

[michael_s]

You have to drop any columns on your osC2.2 db that are not in osCMax, otherwise the data will not match the structure, and errors will keep stopping the import.

Note, just running mysqldiff does not actually convert the database. All it does is create the sql batch for you, then you have to manually run that batch file on the database using phpmyadmin or the mysql command line.

[tcshadow]

I've finally managed to get an error free batch file and made the modification to the osc2.2 database... I was still having issues with the import from there but I'll get it soon I'm pretty sure.

I think what's causing an issue for me at this stage is that my oscmax db had some extra non vanilla columns or tables