What db tables should I copy to transfer orders info from VM2.0.18a to 2.6.6?

[borro]

Hello.

It turns out that even in new VM versions I need to apply some core hacks to make VM working my way. So I think it will be faster to copy orders information from old VM 2.0.18a version by means of PHPMyAdmin than to update the current VM shop and then make a bulk of hacks again.
Please tell me which db tables are involved in storing of order information.

By the way. With new orders new users were registered. So please tell what users tables should I copy also

[dorkus]

i am looking for the same info.... have you found what is needed? you also need jos_users!

we also need to export all products we have in an 2.0.18 install and import them into 2.6.6 - it seems there are tons of different columns in 2.6.6...

any idea?

[GJC Web Design]

why not just upgrade as your supposed to? Then all DB changes are migrated

[borro]

Hello. Sorry, I didn't find the answer because there is no big need now to store all orders in e-shop... may be in future...
Such export/import is usefull in case when you are working on a new shop version and making hacking the core of it at the same time. And while this prolonged process you recieve a few new orders at your working e-shop that still works on the previous engine version. To make this update process again is long way. It's easier to simply copy some db entries in a new shop.
Let it be the feature request to make VM be able to export some checked orders into some .sql file and then import it into some new VM based store

[dorkus]

well, we upgraded the old shop from 2.0.22 to 2.6.6 and then copied all the tables jos_virtuemart_* incl. jos_user* over to the new install of 2.6.6

on both versions i cannot change save / add new products because there is something wrong with the products table?

when i change product i get:

Code Select Expand

vmError: Product store TableProducts: :store fehlgeschlagen!
Unknown column 'product_gtin' in 'field list' SQL=UPDATE `enough_virtuemart_products` SET `virtuemart_vendor_id`='1',`product_parent_id`='0',`product_sku`='FV001',`product_gtin`='',`product_mpn`='',`product_weight`='400.0000',`product_weight_uom`='G',`product_length`='0.0000',`product_width`='0.0000',`product_height`='0.0000',`product_lwh_uom`='CM',`product_url`='',`product_in_stock`='0',`product_ordered`='0',`low_stock_notification`='0',`product_available_date`='2013-11-13 00:00:00',`product_availability`='',`product_special`='1',`pordering`='0',`product_sales`='0',`product_unit`='KG',`product_packaging`='0.0000',`product_params`='min_order_level=\"\"|max_order_level=\"\"|step_order_level=\"\"|product_box=\"\"|',`intnotes`='',`metarobot`='',`metaauthor`='',`layout`='0',`published`='1',`created_on`='2013-11-13 07:51:59',`created_by`='42',`modified_on`='2014-06-09 12:04:10',`modified_by`='42' WHERE `virtuemart_product_id`='96'

i then tried to use db tools and upgrade them it gives me:

Code Select Expand


        vmError: alterTable ADD enough_virtuemart_products.product_gtin :
        vmError: alterTable ADD enough_virtuemart_products.product_mpn : Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` ADD product_gtin char(64) FIRST
        vmError: alterTable CHANGE enough_virtuemart_products.metarobot : Unknown column 'product_gtin' in 'enough_virtuemart_products' SQL=ALTER TABLE `enough_virtuemart_products` ADD product_mpn char(64) AFTER product_gtin
        vmError: alterTable CHANGE enough_virtuemart_products.metaauthor : Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` CHANGE COLUMN `metarobot` `metarobot` VARCHAR(400)
        vmError: Tableupdater updating table enough_virtuemart_products throws error Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` CHANGE COLUMN `metaauthor` `metaauthor` VARCHAR(400)

how can i solve this mess??

please help!

[PRO]

http://forum.virtuemart.net/index.php?topic=103041.0

[dorkus]

tnx for the link, but i am not sure how this helps resolving my errors when trying to save a product?

[dorkus]

i added a column to the _products table in the db for "product_mpn" & "product_gtin" and now i can save again without error. but i am not sure... when i try to update in db_tools i still get the same error as above. what are those two mpn & gtin for? what do they do? what is the proper setting for the columns?

[dorkus]

cmon guys? i am sure some of you have experience with this?

[PRO]

cmon guys? i am sure some of you have experience with this?

did you try "install or update tables" ?

[dorkus]

yes...

when i do this this happens: i then tried to use db tools and upgrade them it gives me:
Code: [Select]

        vmError: alterTable ADD enough_virtuemart_products.product_gtin :
        vmError: alterTable ADD enough_virtuemart_products.product_mpn : Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` ADD product_gtin char(64) FIRST
        vmError: alterTable CHANGE enough_virtuemart_products.metarobot : Unknown column 'product_gtin' in 'enough_virtuemart_products' SQL=ALTER TABLE `enough_virtuemart_products` ADD product_mpn char(64) AFTER product_gtin
        vmError: alterTable CHANGE enough_virtuemart_products.metaauthor : Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` CHANGE COLUMN `metarobot` `metarobot` VARCHAR(400)
        vmError: Tableupdater updating table enough_virtuemart_products throws error Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs SQL=ALTER TABLE `enough_virtuemart_products` CHANGE COLUMN `metaauthor` `metaauthor` VARCHAR(400)

[Milbo]

Then just use it again.

I really wonder what you do. The table updater in vm2, updates your tables from 1.9.8 up to vm2.6.6 completly secure. And you should NOT changes the tables yourself, the changes maybe corrected by the table updater.