I’ve seen during info sessions that in Servoy 5 you can enter a master database and several clone databases.
This is done to update your databases in a Saas solution.
Does dit work only on import on a solution, or does this also work in a development environment?
For example:
Programmer A is using the master database
Programmer B is using a clone database
Thet both use the same codeset (solution)
In case programmer A adds a new field to the database, are all clone databases updated automatically?
Because now I have situation (4.1.5) that programmer A adds a new field and then programmer B can not test his solution, because that clone database is not updated automatically.
And even when programmer B doesn’t use the new field added by programmer A, his solution doesn’t work anymore because this new field is in the repository.
@ Servoy: Could it be made possible that when a new field is added, that an error exception is only thrown on moment of use of this new field and not on use of the foundset? This would also help to reduce the number of databases updates (specially when you have all user databases in your development environment for testing and support.
Does dit work only on import on a solution, or does this also work in a development environment?
It only works on import. Not sure what you mean with field creation, do you want to say that table modifications in table editor ( add/modify/remove ) should also be done on server clones ?
lvostinar:
Does dit work only on import on a solution, or does this also work in a development environment?
It only works on import. Not sure what you mean with field creation, do you want to say that table modifications in table editor ( add/modify/remove ) should also be done on server clones ?
Yes, because now I have to run all the time update scripts on all clone databases in the development environment.
Each programmer is working on the same master database/repository, but needs to test his application on a certain database (using switchServer() statement)
And in case the master has a new field (indeed in the table editor), then the programmers that are testing on data in a clone database, are getting errors.
So 1 single field added in the master, means that I have to update 8 clones.
And after updating 8 clones and another person is adding a new field again, then I can do the job again ![:(]( "Sad")
So indeed I would like to see that when a new field is added in the master (using table editor in developer), that also the clone databases are updated, so that other programmers can continue there job without troubles.
Please add a case for this and we’ll see what can be done.