Hi Sergey, Interesting. There's currently no out of the box feature that helps you with that. I wonder if there should be...? Perhaps, it might be quite useful to redefine a table to hold only a subset of its original columns. I'll think about this.
What I can think of, given existing feature sets is: - Defining updatable views as a compatibility layer - Using <excludes> to exclude the "incompatible" columns from the code generator I'd need to learn more about your use-case to perhaps offer other workarounds, ideas. Best Regards, Lukas 2016-05-21 17:42 GMT+02:00 jdoe <[email protected]>: > Hello, > > Is there any way to use jOOQ-generated tables to take advantage of its > SELECTs and persistence operations if I have some column that exists in a > table only for a specific environment. E.g. select(TABLE.fields()) will > fail in case this column is absent? Shoud I generate 2 sets of > table+record+maybe_something_else? > > -- > 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. > -- 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.
