I do not know –exactly- what this means.
When I imported the solution into the server (to deploy it), I got the following two lines of warning:
[warning] The server version of the column ‘proceeding_id’ of table ‘proceedings_dispositions’ in server ‘fcpadb’ has pk constraint while in the import version it has constraint.
[warning] The server version of the column ‘disposition_id’ of table ‘proceedings_dispositions’ in server ‘fcpadb’ has pk constraint while in the import version it has constraint.
I do not understand why this happened. When I imported the solution I selected ‘Override existing default values (in repository) with the default values contained in the import file.’ I did this because I made changes in the database scheme . Before, the two columns mentioned above were part of a composite PK, I changed those columns to Foreign Keys. see below:
[attachment=0]proceedings_dispositions.JPG[/attachment]
I do not understand why the warning states that the server version of those columns have PK constraints, while in the backend database those columns are FK. Also, there are no warnings in developer. In addition, the imported solution is fine while in production. This is the first time that I have a solution in production with unresolved/unfixed warnings. I think this is a faulted PK constraint warning. Am I right?
In developer I have: Servoy version: 5.2.9 - build 1020
In server I have: Servoy version 5.2.2 -build 1002 - os.name=Windows 2003
Any idea about what is going on?
JC
