Page History

...

When developing database applications in a team development environment, considerations must be made on the development database environment. Servoy Developer allows a developer to connect to the database they are developing against.  This This database can be a local database to the development machine, or it could be a shared database on a the database server.

...

• Test data - It is easier to provide test data for all developers and to use the same test data if the database is shared. Also, if test data is updated regularly from a production server, it would be easier to provide changes to development with a shared database.
• Outside database administration - if a non Servoy developer is responsible for the database structure during development, they do not even need to use Servoy to create the database structure when sharing the database.  Changes Changes will be picked up when Servoy Developer starts.
• Maintenance - easier to maintain, tune, and optimize a single database server than many.
• Security Policies - may require data not leave the office via laptops, etc.

...

• Servoy sequences - If you are using Servoy sequences for primary keys (this is the default for Servoy Developer, so if you are not sure, most likely you are using Servoy sequences) and other autoenter values for a database column, then using a shared database for development can be problematic.  Sequences are managed by the application server, in the case of multiple developers, there are multiple application server processes running, so each developer is trying to manage the sequence.  This This will cause errors when adding records to the shared database. With a shared database, instead of Servoy sequences, you should allow the database to manage the sequence and mark the key accordingly in the table editor (db identity).