Bug in the language files database tables

[franzpeter]

Virtuemart does use language tables for categories, products a.s.o.. Those language tables contain an auto increment product_id, while the standard tables have already an auto increment for the product, category or manufacturer id a.s.o. If someone creates products in english language first, everything works fine. If you add an additional language, the auto increment values in the language table are different from those in the standard product table. It can happen, that there is no relation between the product table and the language table. That means that a product may be displayed in the correct way in the standard language, the additional language shows wrong names and descriptions or nothing, because of the different id. Say we have a product called hammer, created in the default language. There are already other products, so we have already five product id for example. If an additional language is added and new products are created with that language we have new auto increment product id in the language file. If you start now to translate a few of those products in the default language, they get a fault auto increment id, because the id is created by auto increment in the language file completely independent from the auto increment id in the product file for example.
I did take a look into other shop system database tables like prestashop, open cart, oscommerce or magento. They all use one time an auto increment id for example in the product main table. All other tables, which refer to that table may receive an additional auto increment id for some reasons or not, but not  the product id, category_id, order_id, manufacturer_id a.s.o..

[jjk]

"Changed language tables using not autoincrement" was comitted to the SVN 10 days ago.
So that problem should be solved in this version:
http://forum.virtuemart.net/index.php?topic=99590.0