Hi Florian, I'm cc'ing this to the jooq-user group, as this might be of general interest...
> I am looking with interest to JOOQ in couple of way that can be useful for > Minuteproject. Not only Minuteproject 4 Jooq but Jooq 4 Minuteproject ;). > > The way you load master data native and then much more faster that with jdbc > metadata and exhaustive (loading enums...). Impressive. > I am using DDLUtils that most of the time works fine but has limitations. Ex > when the jdbc driver is not correctly implemented (ex: sqlite). Indeed, I had thought about this before, too. The reason why I rejected using JDBC's DatabaseMetaData is the fact that part of the JDBC API is poorly implemented even by the best JDBC drivers (this includes Oracle's ojdbc). This is partially because the meta data API is very primitive itself and from an advanced SQL perspective rather useless compared to the SQL 1992 standard INFORMATION_SCHEMA - or for instance, Oracle's vendor-specific dictionary tables. Some insight can be found here: http://lukaseder.wordpress.com/2011/09/11/database-schema-navigation-in-java-2/ So, in essence, it might make perfect sense for you to create a dependency on jooq-meta to navigate essential database objects. Maybe, at the moment, you may be missing 1-2 features, though. I designed jooq-meta as a primary tool for jooq-codegen. So far, I had no need for any of these features: - column nullability - column defaults - column precision and scale - check constraints - storage clauses (e.g. tablespace, index-organised tables, partitioning, etc) - non-unique indexes - grants and users/roles - synonyms > On the other hand do you view case for managing the first set of JOOQ > templates? I have yet to look at this. The recent release was quite exhaustive with the exciting new features added to the jOOQ core :-) Cheers Lukas 2012/2/27 florian adler <[email protected]>: > Hi Lukas, > > I am looking with interest to JOOQ in couple of way that can be useful for > Minuteproject. Not only Minuteproject 4 Jooq but Jooq 4 Minuteproject ;). > > The way you load master data native and then much more faster that with jdbc > metadata and exhaustive (loading enums...). Impressive. > I am using DDLUtils that most of the time works fine but has limitations. Ex > when the jdbc driver is not correctly implemented (ex: sqlite). > > I have also to learn of your distribution aspects (maven/ant) and generic > design. > > Nice job! > > On the other hand do you view case for managing the first set of JOOQ > templates? > > Best regards, > > Florian.
