Oliver Bertuch (Jul 03 2024 at 12:55): Oliver Bertuch (Jul 03 2024 at 12:55):https://github.com/IQSS/dataverse/pull/7369/files#diff-7093017fea2f3f26783632496b1b41ab0399b0c9d2c774225b66db77c5a78253 is a good example why we need integration testing for our migrations. It relies on havin the externaltooltype table around, but this only gets created by a new deployment, not when you run the migrations manually via flyway. Which is bad obviously, as it's not easy to change...
Oliver Bertuch (Jul 03 2024 at 13:00):(Which I am doing right now with my 4.20 DB, applying the migrations on just a database, without a deployment.)
Philip Durbin 🚀 (Jul 03 2024 at 13:12):So as a workaround are you creating the externaltooltype table manually?
Oliver Bertuch (Jul 03 2024 at 13:40):I will try that. Have to be extra careful, because I need to name the constraints, indices and foreign keys all the same
Oliver Bertuch (Jul 03 2024 at 13:41):I'm also thinking about ingesting an extra migration just for us
Oliver Bertuch (Jul 03 2024 at 13:42):I need some stuff like that anyway as I need to migrate our custom licenses and special field type to something else anyway
Oliver Bertuch (Jul 03 2024 at 14:15):Haha V5.4.1.1 fails as well because in v5.5 (where this migration was added) the auxiliaryfiles table was added. Gosh we really need to fix this. I will try to investigate in creating a new baseline...
Oliver Bertuch (Jul 03 2024 at 14:16):(BTW V5.4.1.1 could have just used an additional "IF EXISTS" for the table to mitigate this problem)
Philip Durbin 🚀 (Jul 03 2024 at 14:36):Oh, right. Yes, I think we eventually got better about adding IF EXISTS. :sweat_smile:
Last updated: Nov 01 2025 at 14:11 UTC