Alright. Thanks for the feedback. Let's keep an eye on this... Cheers Lukas
2012/4/11 Ian Clarke <[email protected]>: > I'm sorry Lukas, I didn't - I ended up having to rewrite that code anyway > and so it wasn't necessary to solve the problem. > > Ian. > > > On Wed, Apr 11, 2012 at 12:23 PM, Lukas Eder <[email protected]> wrote: >> >> Hello Ian, >> >> Did you have any luck further investigating this issue where >> identities weren't generated by jooq-codegen? >> >> Cheers >> Lukas >> >> 2012/3/26 Ian Clarke <[email protected]>: >> > >> > >> > On Mon, Mar 26, 2012 at 11:21 AM, Lukas Eder <[email protected]> >> > wrote: >> >> >> >> >> >> >> >> >> >> >> https://github.com/lukaseder/jOOQ/blob/master/jOOQ-meta/src/main/java/org/jooq/util/mysql/MySQLTableDefinition.java#L114 >> >> > >> >> > I tried that, and it's possible I was using Eclipse's debugger >> >> > incorrectly, >> >> > but it apparently didn't hit that breakpoint :-/ Is that possible? >> >> >> >> Line numbers may have shifted. From your code snippets, I guess you're >> >> using jOOQ 2.0.5. The link I posted is from 2.2.0-SNAPSHOT. >> > >> > >> > Yeah, I didn't go by line number, I found the equivalent code in my >> > version. >> > >> >> >> >> > I'll try trace debugging, not that familiar with log4j but I'll >> >> > figure >> >> > it >> >> > out. >> >> >> >> It will be sufficient to put log4j.jar and the log4j.xml file on the >> >> classpath. jOOQ will discover it automatically, then. >> > >> > >> > Ok, I'll give it a shot. >> > >> > Ian. >> > >> > -- >> > Ian Clarke >> > Blog: http://blog.locut.us/ >> > > > > > > -- > Ian Clarke > Blog: http://blog.locut.us/ >
