Ulrich, On Tue, Apr 9, 2019 at 2:38 PM Ulrich Grepel <[email protected]> wrote:
> Nice to hear that 3.12 will solve some more issues. I understand that > backporting is not an option. Any idea on the general timeframe of 3.12 > availability? (days, weeks, months, years... a "logarithmic" estimation > like that would be sufficient for now). > Months, in that case :) But hopefully less than two. > (While DDLDatabase is designed with flyway in mind, it would basically > work with liquibase scripts as well - as long as the liquibase scripts > are plain SQL scripts with comments controlling what liquibase does. > Yes, you're probably right. > For liquibase-with-H2 in gradle there's no need for more code, this > works out of the box using the well known liquibase and jOOQ plugins. No > first hand experience with flyway and its gradle plugin, but that should > be the same. liquibase-with-PostgreSQL or alternatively > flyway-with-PostgreSQL requires some PostgreSQL database. Same with > other databases. Testcontainers only suffers from the > separate-JVM-problem, i.e. you'll end up with two separate > testcontainers if you're trying the same approach as with H2. (With H2 > you cannot use a pure in-memory database for the same reason.) > > The approach I went right now is as I said a variation of DDLDatabase, > using testcontainers-PostgreSQL and liquibase (flyway would be > possible), not using jOOQs DDL parser, not using H2. So basically there > is no limit. What limits with testcontainers do you mean? (other than > the one with separate JVMs which is what the DDLDatabase-variant > eliminates.) > Not all RDBMS are currently supported by testcontainers. I think I remembered you saying that additional RDBMS should be supported in the future. -- 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]. For more options, visit https://groups.google.com/d/optout.
