|
I'm been looking into this and trying to figure out why this is happening.
The version of UPS in bbe1c0e#diff-23e531d12489411024ea5c379be1d178R70 is 1.1.0.Final-SNAPSHOT:
With the addition of the migrator we now have the requirement to create the data base schema using the migrator and not have it automatically created by hibernate upon application startup.
./bin/ups-migrator --logLevel=debug update
|
This would populate the database succesfully with a clean database.
Now, if we take checkout the commit above:
git co -b migrator-qe-issue bbe1c0e
|
Build and deploy against to the server (with a clean mysql database) will create the data base schema, but an incorrect one. Running the migrator against this database will error with the above reported error.
At the time of the bbe1c0e commit ,there was no migrator yet so letting hibernate create the database schema was the way to do it. Now that the migrator was introduced it should be used to generate the schema.
One thought that I had is that you mentioned in the thread that you run an integration test with runMigrator=false. Depending on the version of UPS used it might be possible that it is creating the incorrect database schema
$ ./gradlew --stacktrace :spacelift:test -Pwildfly8UpsFromSource -Pdatasource=mysql -PrunMigrator=false
|
I tried running this on my local machine but it fail but it looks like this is using 1.1.0-beta.3 which does not contain the migrator. So this could indeed be the case that the schema is created upon application deployment instead of by the migrator.
I'm also wondering about the version used to test. Should we not be using a later version to testa against?
|
