v4 on sql server - migration experience

[pvgenuchten]

Today we deployed a v4 on windows with sql server db, some experiences:

• Hibernate throws an error that type variant is not supported -> we updated the sql-server jdbc client to recent version, this one seems to support the variant type
• We used embedded windows authentication to connect to sql server, the jdbc download includes a dll to support this case. Placing the dll in /tomcat/lib did not work, placing it in \system32 is the solution.
• No migration from 3.10 to 4.0.5 is available, is it a bug or a feature we should document?

do you have suggestions on where to fix/document these aspects?

[ianwallen]

@pvgenuchten Regarding "No migration from 3.10 to 4.0.5 is available"

It seems like it is coded to perform 2 migrations. - One for before JPA (3.0.2?) and one after. Versions between 3.0.2 and 3.0.6 are mixed between both migrations - not sure why.

https://github.com/geonetwork/core-geonetwork/blob/c4f1ddde66efbda7a87df223459a9d8641656fe0/web/src/main/webResources/WEB-INF/config-db/database_migration.xml#L33-L40

You don't show the rest of your logs - but I believe the error you are seeing is a result of the first migration because there is no migration path for 4 because it stops at 3.0.6. There should be a second migration section which upgrades your 3.10 to 4.0.5 and that is the one you want to check for errors.

I do agree that this is odd and may cause confusion. Maybe some better messages would help...

[ianwallen]

5866 may help resolve part of this issue.