Hello we use JOOQ/Liquibase for database access abstraction and they work quite > fine. The only minor annoyance that both use own table metadata info and > type system and we continuously have to convert/maintain consistency > between the two representation (and a third one, which is our legacy stuff > :) It would be really grate if the two system can be merged. > > "Merging" sounds easy, but it isn't :-) Consider merging licenses, copyrights, ownership, responsibility, mission statements, etc. etc.
So in a more realistic scenario, the two tools could improve cooperation. Could you be specific about your use-cases? Where do you run into trouble, when meta data info is duplicated? How could this be improved (on the jOOQ side, on the Liquibase side?) Cheers Lukas -- 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/groups/opt_out.
