I think it is a real problem. My existing table names are spelled in some way they just can't look nice when translated to java code. I spent a lot of time creating my own generator strategy. There is little documentation and because I was in a hurry and could not easily figure out the actual logic the *println way*, I ended up calling super and overwriting the corresponding jooq generated name. You said you are are planning to rewrite code generation to turn it into a 2 steps process, but are you going to offer a nicer way to customize Java class and property names on a per table basis?
Something like an XML definition file would be nice, don't you think so? Best Le samedi 12 janvier 2013 09:09:35 UTC+1, Lukas Eder a écrit : > > > Thay was a "I will try to provide a solution once I got enough insight >> into the jOOQ source I just checked out" :-) >> > > Wonderful! Do note that one of jOOQ 3.0's goal is to provide better > extensibility of the code generator to users. Any ideas, suggestions, > contributions in that area are very welcome as well. Maybe, you'll discover > something along the way >
