So it appears that the custom matcher strategies<http://www.jooq.org/doc/3.3/manual/code-generation/codegen-matcherstrategy/>do *not* in fact allow one to work around the the forced URI-encoding of column names. Trying to reproduce getFoo_bar() (which is what jOOQ used to produce for a column named foo:bar) will in fact yield GETFOO_BAR() or GetFooBar(). The only way I can even make it work close to correctly is to use the AS_IS transform to yield getfoo_bar(). This is workable, but frustrating.
I would even go so far as to consider it bugs that the strategies require that "get" and "set" be provided in the output of <fieldSetter> and <fieldGetter>; and that the transform is applied to the "get" and "set" suffixes as well. OK, I'll use what I got sort of working. But can someone tell me what <fieldMember> applies to? -- 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.
