If you are doing a store import from V2 to V3, suggest that you do the following in your V2 store before performing the import:[list]
[]Administration/Logs - clear logs
[]Administration/Statistics - remove statistics
[/list]
This will save you hours and hours of wait time for things like “Backing up data for: cscart_stat_banners_log” or the “cscart_new_orders” table and a variety of other data/info…
[quote name='tbirnseth' timestamp='1356048269' post='151533']
If you are doing a store import from V2 to V3, suggest that you do the following in your V2 store before performing the import:[list]
[]Administration/Logs - clear logs
[]Administration/Statistics - remove statistics
[/list]
This will save you hours and hours of wait time for things like “Backing up data for: cscart_stat_banners_log” or the “cscart_new_orders” table and a variety of other data/info…
[/quote]
Very good advice. I found this out the hard way the first time I tried to do an import.
Yeah, should also empty the buggy and useless cscart_new_orders table. This should never even be ther unless Twigmo is installed and then it should be updated by a hook and not from the fn.cart.php file…
Man, wish I had known to look for this, it really should be in the documentation. I've been waiting for 30 minutes for that freaking “cscart_stat_banners_log” and went into PHP admin and almost fell out of my chair. WTF?
We'll see how it goes, might have to cancel the import, restore the version 3 db and start over.
Although I do not know what the table cscart_new_orders is exactly used for, it's been in the data base since at least 1.3.5 so I doubt that it is used solely for Twigmo.
Search the whole source tree for “:new_orders” and I think you'll find the only “read” of that data is from the Twigmo addon.
I couldn't tell you Tony. I actually have orders since day 1 in that table so it's been there since 1.3.3 or 1.3.4 (I can't remember exactly what I started with). I don't think Twigmo was even thought of back then.?
Who knows. I can only report what I find. That it creates a row for every admin (and there have been bugs where it creates a row per user) for every order means that the table grows at an awesome rate. I found it bogs down a store import and have never seen where truncating it has caused a problem.