Hello, > I didn't do the alias impl. It was the original reason why > I wanted the columns to be instances. But the aliasing was used only once > so put it in the backburner.
I see. TableImpl is used once or twice in other contexts than when subclassing it in generated code. I guess you might run into trouble in those other rare cases, if you don't modify it (e.g. when using aliased tables along with SchemaMapping). > Suggestions in the code generation part would be > The variable declarations had full class names (with package). That made it > hard to read. I know, it can get very hard. But unfortunately, that shouldn't be changed in general. There had been an important bugfix in 1.6.2: https://sourceforge.net/apps/trac/jooq/ticket/651 Imagine, you have tables / procedures named "STRING", "INTEGER", "TABLE_IMPL" etc... Nothing will compile anymore, if your generated classes don't fully qualify everything. > We generate all the table references in a single interface. Makes it easier > to import. Nice, I had the same idea for jOOQ 2.0: https://sourceforge.net/apps/trac/jooq/ticket/924 Cheers Lukas
