On Wednesday, 5 September 2012 12:25:13 UTC+1, Lukas Eder wrote: > > > Not knowingly, although I have noticed HSQLDB throw some errors when > > accessing the DB meta-data during the DDL generation phase (which is > > upstream of the JOOQ generation phase), so I will look into that. >
So I think the root cause of this bug is some kind of strange interaction with HSQL during the DDL generation phase of our build that renders the INFORMATION_SCHEMA in HSQL useless, and I have no idea why. So I have a workaround for this specific issue which basically involves making 110% that the project is clean before any DDL generation or it's subsequent application to an HSQL instance is performed. In other words, the root cause has nothing to do with JOOQ. > >> Can you provide log4j debug-log > >> output from your code generation? > > > > I've attached the output from the codgen. > > I'm sorry, by log4j debug-log I meant using log4j with something like > this configuration file here: > https://github.com/jOOQ/jOOQ/blob/master/jOOQ-test/src/log4j.xml > http://logging.apache.org/log4j/2.x/ > > It should be sufficient to put log4j and the log4j.xml file on the > classpath for the code generator > The interesting thing about the INFORMATION_SCHEMA being made unavailable for JOOQ code gen is that the codegen succeeded, but the table classes were extending TableImpl instead of UpdatableTableImpl. Doing a mrproper clean before attempting the codegen now results in inheritance from UpdatableTableImpl, so the problem is solved. Unfortunately I've tried a lot of different configurations for log4j to get it to log something sensible, but alas, I'm struggling to get it to work. I think this is a product of using a maven build that uses logback all over the place instead of log4j, coupled with the general maven classloading issues. I'll try to see if I can convince it to output something, in order to track this down. Cheers, Ben
