Hi, regarding the code generation i have to add my two euro-cents: first cent: please please seperate the generation code into two phases a) prepare completely all meta-information b) write the Javacode second cent: i would like to have more flexibility. E.g. make it possible that i access the results of the db examination and write the results in my own XML file. Than let me write code to build the Factory,Schema, Table, etc. objects in memory (no code generation) by myself. What is it good for? It opens possibilies for the dynamic usage of jooq. D'accord, this is a niche but on the other hand, if you follow advise 1, you are almost there. let me know, if i can help. regards, Manfred
Am Freitag, 31. August 2012 09:48:54 UTC+2 schrieb digulla: > Hi, > > I've started to write a new Xtend-based code generator for jOOQ 3.0. The > main focus here is to simplify the code generator and to make it easy to > reuse. > > For my test cases, it would be great if I had a "MockDatabase" where I can > define schemas, tables and columns in a unit test. Does something like that > already exist? > > Regards, > > A. Digulla >
