Hello Incomedia ...please clarify this unique database point for one prpject.... 
Autor: Axel Hello Incomédia,
In this post, it's clearly explained that it's not possible to declare more than one database by project in the future version.
When I develop a project I am using a local database (localhost) to do development and testing.
When I export the project I have created an other database connector (into WSX5) to the provider and I choose the correct tables into some few WSX5 settings before to export with the good database parameters.
If I need to continue to develop locally, I change again some tables pointers into the project, and I am using again the localhost database.
So with the next version this situation will not be possible any more.
I don't undertsand well how to develop with locally db and when ready to export with the good database paremters for the db provider.
Please could you clarify this point
Thanks
Axel
Hello. I sent a notification about your question to the company employees, expect an answer from them here in the comments.
Hello Axel
In this case, you will need to change the Database connection data every time you export to a different place. The situation isn't much different from before except for the fact that you can't store the Database data aside to switch but need to reinsert them at every change
Go to Step 1 -> Data management and change the DB data when you need to export locally, and then again when you need to export online. It should work that way
Try it out and keep me posted here
Thank you
Stefano
Autor
Hello Stefano,
Ok
I understood well. I was that I thought
I considere this new is more restrictive than useful. Before it was possible to have x DB and just need to select 2 paramters before to use it. Was easy to do.
Now we need to re-configure the software at each time !!!
Stupid decision from your side. And I never saw any requests on the Help Center about this feature from any user.
The best should be to have the choice to keep actual configuration or to move to the new one...
Now it's mandatory to move to this new one... with no choice.
It's a restrictive update for me.
And already some posts about data lost during migration.
Axel
Hello Axel
Yes, we understand that for such a situation it might take a little longer, but we really felt like this update was going to help a lot of users which are not very familiar with things like XAMPP and similar, which are quite advanced, which in the end is the type of person the software is mainly targeted to.
We receive many support requests on issues with Databases and we're sure that with this update, they will become less frequent in the future
I hope our choice makes more sense now
Thank you
Stefano
Autor
It's was easier for Incomedia to block any project with One Db that to fix or to manage a project with X databases which is a little more complex...
So it is a solution by facility for you with no offer for more experts users.
In fact our knowledge is too big for your users target like you said yourself.
So i continue to say this feature is restrictive...and not very useful !
Axel
I agree with Axel here, i have not updated yet and would like to see the use of more databases to be kept.
beside the use of xampp i would like to work on my databases myself, make backup's from mysql and so on.
If it's all in 1 database error's and problems are immidiatly bigger, backups are bigger. I can't create a test database / envirement.
I don't like this update eather, maybe it's an idea to set this for EVO, but keep it in the PRO version. I would like to think that the PRO version has not only more options but is also way more suitible for PRO users! Or at least Users that have a little bit more experience with coding / programing and so on.....
For instance, to get Mollie payment working correctly i made extra fields in the database and update these seperatly to keep payment for my store good and clear.
If i have a problem with the poll database i don't care, ok, the poll does not work anymore, but payments do. So i like to keep the payments / order database as clean as possible.
Autor
I am full agree with Andre...
The pro version is for pro users ... So the idea to keep 1 database per project should be into Evo version only.
I the user bought a Pro version it is because the user is more pro...
Thanks Andre, because it is the best reason to keep x database into the Pro version...
But easier for Incomedia to support the software.
Like said Stefano "... to help a lot of users which are not very familiar"
Their target is just novice user...
We... expert users are into their target... Business = money is their target with novice users....
not us.
Axel
+1
I also fully agree with Axel and Andre: the PRO must be PRO not only in name but also in its functionality