On Wed, Dec 30, 2015 at 12:34 PM, Lukas Eder <[email protected]> wrote: > No. Maybe in jOOQ 5.0 :-)
OK, cool - then this means that is fair to say that JOOQ is a JDBC tool. If that is the case I would like to see less assumptions being made by the JOOQ runtime about how an app wants to interact with the DB with a transaction. But in fairness, my comment is a bit off topic - this thread is about the code generator, not the runtime. > Interesting feedback. So, were you really missing something from the runtime > library or from the code generator? When I mentioned type index I was talking about the private maps TYPES_BY_NAME, TYPES_BY_TYPE and TYPES_BY_SQL_DATATYPE which are all immutable to the third party code during code generation and at runtime. What I'd like to be able to do is to write into these maps so that (a) I don't have to override JavaGenerator on a per-column basis to shadow the output of these immutable indexes (b) When I generate field references for complex queries at runtime, that the DSL.field() call can be aware of my custom type - this is another instance where the immutable type map leads to bogus SQL being generated at runtime. -- 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.
