Am Mittwoch, 11. Juli 2012 14:44:28 UTC+2 schrieb Lukas Eder: > I like the idea of the strategy but I don't understand how your > > implementation works, so I'm stuck to solve the problem in the place > which I > > understand :-) > > I see. You will have to be a bit patient on that one. I can't give you > a promise as to when I'll find time to come up with nice documentation > examples for that. I personally prefer to improve the jOOQ Console > documentation, first. > > > But how about this idea: The generator keeps a list of methods (with > > signature). When you need a new method name, you can give it a list of > names > > (most desired first) and it tells you the first one that's free? > > I don't see the immediate use-case for that. Could you explain, please? > Note that I think that that these "extreme" customisation ideas are > best implemented by allowing for complete code generation > customisation, which is what jOOQ 3.0 should implement. >
One use case is a large model where you might want to split tables into Java packages. In our app, the table names are prefixed with module names, so the strategy must be able to turn ADM_USER into *.adm.User. Depending on time/pressure, I'll try to create a pull request for a new code generator but since my time is limited, I'll probably write it in Xtend. That wouldn't add any runtime dependencies on jOOQ, it would only add 2-3 runtime dependencies on the code generator. Regards, A. Digulla
