After exporting a multi-module solution on one machine, then importing into Servoy on another, I get one or more of the following errors upon opening the solution on the destination computer:
Relation ‘contact_to_commitments’ has no keys (is empty)
Upon examination of Relations, the keys are indeed missing. These are relations that have been around and functional for a long time in the solution. The name and options are unchanged; it is just the key assignments that have gone missing.
Both machines are MacBook Pros w/ latest OS, Java, Servoy.
It doesn’t happen when importing the solution to other machines (MacBook, G5 iMacs).
Do you mean some of the tables lack a primary key after you have imported the solution? If Yes,
We have seen this problem several times when importing ‘old’ solutions. It is very irritating to have to check and fix all the primary keys. What will make this problem worse:
no primary key constraint in table (without this Servoy can’t work out what the pk is)
table created outside servoy
With postgreSQL, Servoy sometimes guesses the wrong SEQUENCE names when importing 2.x into 3.x
Yes, the primary keys are absent. The relationships are there, but without primary keys assigned.
The solution was initially developed in Servoy 2 (tables created within Servoy), but has been updated as soon as each new version comes out. As we are two developers working with modules (and sometimes at different locations), there have been dozens of imports of one or all modules in order to keep current with one another. Only very recently did the problem with disappearing keys manifest. So, it may be a problem with the latest release. Or, it could be something (but what?) specific to the destination machine.