Table Orders in database changed 
Автор: Václav K.Hi,
I've just noticed that new orders starting from 2121/08/08 are no longer stored in table Orders in the database. Why is that so? I created new tables and views to be used for events like Christmas, to help us with orders management. They aleready worked well during last test at Easter. They take data from the Orders table (among others). Now I have no data in my new tables and views and likely to have to rewrite all my work as the data suddenly not present in the Orders table.
There is a new table w5_81d1f39b_cart_orders, where I can see the new orders.
But with those strange changes, no proper work is possible in the database.
Please do not change table names and the main functionality unless urgent. Please let us know beforehand if that should happen. I don't like any unpleasant surprises during the season.
Thank you for the explanation.
Vaclav
Hello Vaclav,
You are right. Incomedia has changed the DB management to have now just only ONE DB by project... For us, pro users it is not appreciate because it is restrictive update of version. Many posts on the Help Center about this... Nothing has changed and they keep their position...They don't lsiten their customers.
In parallel they changed the tables name with a random prefix like w5_81d1f39b in front of all tables. And now the project is using these tables and not old.
So now the table names are not generic but specific for each project !!!! Stupid ! or voluntary to block usage of external tool based on their DB... In this case you need to configure / compile the external tool for each configuration.
Again it is a stupid decision never ASKED BY USERS
Why Incomedia does not keep the original table names ?
Mystery ?
May be a serious explanation from them should be welcome
Enjoy!
Axel
Автор
Hi Axel,
Thank you even for this dissapointing explanation. Weird... Many hours of my work lost due to this change.
I can imagine there are hundreds or thousands of users influenced. Many may have even created sophisticated expensive solutions using the database and now this, without any discussion or notice...
Best regards
Vaclav
+1
Hello Vaclav
I apologize for the issue this might have caused. As far as the internal logic of the software is concerned, we make changes so that the user has the least amount of configuration to change, but of course, we cannot guarantee complete continuous compatibility with external code
In any case, this change is only necessary when upgrading an older project to the new v2021.3 and the same situation should no longer occur in the future
I remain available in case you have any further questions
Thank you
Stefano