Multiple Developer Merges, DB Changes, and Import Errors

Classic Servoy
1

Hi,

We’ve got developers in two locations working on one solution. Each location has it’s own local copy of the backend database and we are merging developer exports daily to get new solution code in one .servoy file.

We’ve run into a problem when we want to change the solution’s database(s).

  • One developer adds columns to a table, updates the solution, performs a merge, and exports it.

  • The new columns are added to the other location’s database and the export is imported and fails with errors about “duplicate fields”.

It looks like Servoy is trying to create the new fields during the import but they already exist(?). We are completely deleting the solution from the import repository before import so I don’t understand why Servoy would try to create those fields instead of seeing they exist in the DB.

Our workaround is to delete the fields from the import database and let Servoy create them, but this is very troublesome as the fields are created in seemingly random order which is confusing for tables with lots of columns.

Any help is apppreciated.

Thanks.

2

Hi JDW,

This sounds like a problem I have all the time, but the solution is really simple :wink:

Restart your Servoy server before importing into the Repository.

What is happening is that Servoy Developer is adding fields to the backend database. Servoy Server does not know about these since they didn’t exist when it was started, so it tries to add them again. If you restart, Servoy Server becomes aware they already exist…