Mendix 3 and shared data database

Can you use Mendix 3 with multiple developers using a shared database? I have not tested this yet, but I imagine that local (uncommitted) changes in the domain model are applied to the shared database when deploying. When somebody else deploys the changes are undone leading to strange runtime errors. At least this is our experience with Mendix 2.5 when people do not refresh if the get the sync database message and notice other peoples changes being reverted. With Mendix 3 the question is whether the database updating is altered or that we should always commit domain model changes asap.
2 answers

Yes Bart this is working as you expected, so you can potentially have different domain models (thus database schema's) when you are working on uncommitted features or your colleagues have not updated yet. I wouldn't recommend using the same database in these situations.

Also note that even if your changes don't lead to a database change, they could still mean that data becomes corrupt. For example: You added a new attribute to an object and committed it. Then your colleagues update but you then decide that that attribute should be required. So you change it and even commit the change but your colleagues don't update. This means they can create instances of that entity that are 'corrupt' according to your domain model.

In general, I'd say just use your own database during development.


The database updating is indeed altered it is now managed by svn versioning which makes it easier to handle conflicts between forms/database changes and microflow changes. Whether you want to commit a certain change or not really depends on the situation. On how life changing they are.

But as a rule of thumb we have agreed to update only untill the functionality you are working on is finished.