Greetings,

I have used Liquibase previously with success, and preferred its 
SQL-agnostic migrations versus Flyway.  Personally I did not want to 
remember the minutiae for auto-incremented PKs versus sequences, etc. as my 
projects tend to use an embedded database for unit tests (H2, HSQL), and a 
different database for integration tests.  My tables have been simple 
enough to get away with this.

In terms of DDL, almost all of my Liquibase logic is expressed in XML or 
YAML.  jOOQ DDL would be interesting if there was a non-Java DSL or there 
was a tool to automate the Liquibase script to Java code.


On Tuesday, June 21, 2016 at 6:41:12 AM UTC-7, Lukas Eder wrote:
>
> Hey Adam,
>
> Thank you very much for sharing this. This looks very interesting. A nice 
> addition to our existing Flyway examples.
>
> I'm curious: What made you choose Liquibase?
> Also, given that you have experience with Liquibase and jOOQ: I'm 
> personally curious. Is there any potential that jOOQ's DDL support could 
> replace Liquibase here?
>
> 2016-06-14 6:38 GMT+01:00 Adam Zell <[email protected] <javascript:>>:
>
>> Hello,
>>
>> I created a Maven project to show the process from soup to nuts: 
>> https://github.com/azell/jooq-combined
>>
>> * Liquibase is the migration framework that uses H2 to auto-generate jOOQ 
>> code into a JAR
>> * Application code layers Spring Transactions on top of the JAR for 
>> various CRUD operations
>> * The TestNG unit tests exercise several dialects for embedded databases
>>
>> Any bugs or suggestions appreciated.
>>
>> -- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.

Reply via email to