We have column names like "foo:bar" I accidentally used jOOQ 3.1.0 to generate class names. I created a new ExampleRecord and called exampleRecord.Foo_bar() to set the "foo:bar" column. OK, that looks reasonable.
Then I tried to compile and ran into the problems that arise<https://groups.google.com/d/msg/jooq-user/mmwfznnCdJ0/QTs3z-6XSaYJ>when mixing version numbers. So I updated the code generator to version 3.3.1 to match the library used in my code. Now instead of exampleRecord.Foo_bar() I have to use exampleRecord.Foo_3abar(). (groan) The source of the bug is easy to guess: somewhere the generator is URI-encoding encoding the column names (but why!??) yielding "foo%3abar", so that when they get "cleaned up" and camelCased for Java this gets turned into "foo_3abar". Ugh, this is just ugly. Could we get a patch release quickly that fixes this bug? Otherwise we're going to have to have tons and tons of code that looks terrible, which will have to be updated when the bug is fixed. (I'm just now going through and changing all my colleagues' JDBC code to jOOQ; this isn't going to help it sell well on my team.) -- 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.
