On Fri, May 31, 2024 at 3:48 PM 'Bernd Huber' via jOOQ User Group < [email protected]> wrote:
> how could jooq-migrations detect, when a changeset has changed. > Other migration-frameworks would compare the SQL in the Changeset/File > with the SQL in the "Protocol-Table" (in liquibase this is the table > DATABASECHANGELOG, or in play-framework "play_evolutions") > But because the generated SQL of jooq could also change with > versions-upgrade of jooq (when you found a better way to build some SQL), > i think that you can not use the SQL for detecting the change. Maybe you > even need to save the Codeparts in the Java-Class that contains the > Jooq-Code for migrating. > So if anything is changed in this Java-File the migration needs to be > marked as changed, or something like that. > There's always a bit of "input source" for any change, e.g. SQL that is parsed by jOOQ but written by you, git hash for the relevant file, etc. It doesn't matter what jOOQ renders for your input SQL (including you changing settings, such as case sensitivity settings, etc.) -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO6wW1SY8WeKUPNe2AenQLL5i2fmXN6geEZC2o3_ui_AAw%40mail.gmail.com.
