I would like to optionally exclude a column from being added to selectFrom (and similar) queries based on some runtime information. I don’t see a way to do this, but perhaps I am just not seeing a configuration option?
In general, it seems like this would be a useful feature for supporting incremental, additive changes to data models. So, if this isn’t currently supported, what are your thoughts on adding this as a feature? Some more context: I maintain a component that has some database tables backing it, and it is used by many different applications. I created a row in the database schema to define the “library schema” version to support eventual modification of the data model that would let me support multiple versions of the backing datastore with one version of the library code. I would like to add a column to these database tables which I would only try to write/read if the library schema version has been incremented. However, I have many usages of selectFrom. If I add this new field to the jOOQ generated code, then all selectFrom queries on affected tables fail for users that haven’t migrated because that field doesn’t exist. So, I’d like to blacklist this field based on the value of the library schema version. -- 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.
