Hello Alex!
You have provided an excellent possibility to import data from the existing 1.13 to 2.0 versions. However, if the default table format of v2.0 is not the same than 1.13, what should one do? The best is to recreate a new table from the 1.13 defs and integrate then into v2.0 and make new defs + table. Then import could be flawless and would be upgradable for any versions and format. This actually also allpies to all other products.
The best would be to specify what fields needs to be imported and if the fields needs to be added during the imports.
It is a lot of headache to export the database tables in 1.13 and then import into 2.0! What about the category information that is in terms of numbers i.e. CatIDs. If the CatIDs are missing some IDs then during the re-import they will loose their links to the original categoryIDs, since it would then point to a wrong ID. Export does not actually export the real category name and thats the problem.
You have provided an excellent possibility to import data from the existing 1.13 to 2.0 versions. However, if the default table format of v2.0 is not the same than 1.13, what should one do? The best is to recreate a new table from the 1.13 defs and integrate then into v2.0 and make new defs + table. Then import could be flawless and would be upgradable for any versions and format. This actually also allpies to all other products.
The best would be to specify what fields needs to be imported and if the fields needs to be added during the imports.
It is a lot of headache to export the database tables in 1.13 and then import into 2.0! What about the category information that is in terms of numbers i.e. CatIDs. If the CatIDs are missing some IDs then during the re-import they will loose their links to the original categoryIDs, since it would then point to a wrong ID. Export does not actually export the real category name and thats the problem.