2014-04-28 23:48 GMT+02:00 Garret Wilson <[email protected]>: > 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. >
Yes, we've had this discussion recently, on the user group: https://groups.google.com/d/msg/jooq-user/1iy0EdWe_T8/TtgmseBsjiUJ We might address this some time soon: https://github.com/jOOQ/jOOQ/issues/2924 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. > How would you go about people not wanting "get" and "set" in their getter and setter names? > OK, I'll use what I got sort of working. But can someone tell me what > <fieldMember> applies to? > It is used for member names in POJOs and also for method argument names. See: http://www.jooq.org/doc/latest/manual/code-generation/codegen-generatorstrategy/ /** * Override this method to define how Java members should be named. This is * used for POJOs and method arguments */ @Override public String getJavaMemberName(Definition definition, Mode mode) { return definition.getOutputName(); } -- 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.
