11 replies to this topic

[ggrant3]

I am finally going to start working on switching over to the 2.3 version but I was thinking about something last night. Is the db for v2.3 the same as v2.2(RC).

Could I just upload the files portion only and point them to the current db?

Also, is there a specific faq area/thread for the 2.3 version because I have a few questions that most likely have already been answered but I can't find much in a search on here because typing in "v2.3" doesn't produce any results.

[DunWeb]

@ggrant3,

NO, there are differences between the two. If you want to use your RC database you will need to integrate it into the v2.3.1 tables....the IMPORT function will not work.


Chris

[ggrant3]

Oh okay.

What would be the proper way of uploading the current information then? I was going to install Easy Populate for the products, but for the existing customer data and sales what should be done?

[geoffreywalton]

Migrating 2.2 to 231 involves adding fields, removing fields, changing field sizes adding keys etc.

Also the link between customer and address book needs to be migrated.

When I do it, I use mysqldiff, an open source application, to do most of it.

HTH

G

[ggrant3]

Oh, wasn't expecting it to be that involved, now I'm getting a little nervous

[geoffreywalton]

Just read the 2.3.1 upgrade documentation, it is easier than I described above.

Just the data in some of the dbs I converted was a little flaky.

e.g. not all products had images.

HTH

G

[14steve14]

I used phpmyadmin and uploaded the individual tables to my computer in csv format. Opened the files in excel and altered the tables so they matched and uploaded them again. It worked as a test, but it did take a while doing one table at a time. I did also find that you can save a csv file with the column names at the top.

[ggrant3]

I have tried a couple times to upgrade to the 2.3.1 version and something is wrong. As a stock osc site everything functions fine, but I can't get any of my customer or order history or any of my products to appear.

I have done this process a couple of times I still have no customer, or order history and my products don't show up.

What I have been doing is:

• create a backup database of my current shop
  
• create a new database
  
• modify the new database to the 2.3.0/2.3.1 standards (per the upgrade guide making the sql changes)
  
• upload the 2.3.1 catalog files
  
• go through the installation process
  
• then the new 2.3.1 shop works fine as a "new" store, but it doesn't show any of my existing data.

By starting out with an existing database and then converting it (per the 2.3.1 upgrade guide) shouldn't all of my customer & order history & products appear?

Am I leaving a step out?

[geoffreywalton]

the installation overwrites the db.

You can edit oscommerce.sql in the installation folder so it does not overwrite certain files

HTH

G

[ggrant3]

geoffreywalton, on 09 February 2012, 15:20, said:

the installation overwrites the db.

You can edit oscommerce.sql in the installation folder so it does not overwrite certain files

HTH

G

Ooooo, yeah I guess I can see that happening....um..now. Just went through the stock files and I see what you mean. I didn't realize there was a database file in there that was overwriting my db that I put in and updated 5 mins before. But I guess there would have to be in order to setup the stock db, whoops.

So correct me if I am wrong (which I may be ) but could I just upload my database again, modify it to the 2.3.1 requirements, and then modify the oscommerce.sql file like you mentioned but just have

DROP TABLE IF EXISTS counter;
CREATE TABLE counter (
  startdate char(8),
  counter int(12)
);
DROP TABLE IF EXISTS counter_history;
CREATE TABLE counter_history (
  month char(8),
  counter int(12)
);

as the only code in there. I looked and it doesn't seem that there are any other references to "counter" anywhere else in that file (other than that small section of code) so it doesn't seem like removing everything else in that file and leaving only that piece of code would cause a problem. Well besides erasing my current counter information which I can simply re-enter via the database anyways.

Or is there a different recommendation you have that may be better, safer, or easier?

[ggrant3]

ggrant3, on 09 February 2012, 16:08, said:

Ooooo, yeah I guess I can see that happening....um..now. Just went through the stock files and I see what you mean. I didn't realize there was a database file in there that was overwriting my db that I put in and updated 5 mins before. But I guess there would have to be in order to setup the stock db, whoops.

So correct me if I am wrong (which I may be ) but could I just upload my database again, modify it to the 2.3.1 requirements, and then modify the oscommerce.sql file like you mentioned but just have

DROP TABLE IF EXISTS counter;
CREATE TABLE counter (
  startdate char(8),
  counter int(12)
);
DROP TABLE IF EXISTS counter_history;
CREATE TABLE counter_history (
  month char(8),
  counter int(12)
);

as the only code in there. I looked and it doesn't seem that there are any other references to "counter" anywhere else in that file (other than that small section of code) so it doesn't seem like removing everything else in that file and leaving only that piece of code would cause a problem. Well besides erasing my current counter information which I can simply re-enter via the database anyways.

Or is there a different recommendation you have that may be better, safer, or easier?

Well that doesn't work.

I guess I will have to pick apart the db file.....fun

Maybe I am missing a valuable piece of information but it seems like this process is awful difficult for me to get implemented.

Edited by ggrant3, 09 February 2012, 17:35.

[geoffreywalton]

You just need to work out which tables contain the data you want and delete the drop and create and insert command for each table you do not want overwritten

Categories, cat desc, all the products, manu and manu desc to name the ones I can think of off the top of my head.

HTH

G