Hi there, I'm looking at using JOOQ for a project, and am curious about the idea of using the code generation once per new table, then keeping these objects updated manually afterwards as the database schema evolves. We are planning on doing migrations without downtime, so we'd like the flexibility to be able to rollback if there's a problem with an update, so code needs to be able to work with a pre-migration and post-migration database.
What do you think about that idea? Would it be better to just forgo the code generation features in my use case? --patrick -- 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.
