Hello Marc, >>Yes, chances are high that you may use jOOQ out of the box using JDBC >>meta data for the code generator, and SQLDialect. > > Ok cool, but how does that work in detail? > Is there a code generator for > such cases?
It doesn't work yet, as this feature is not yet implemented. Once implemented, there will be a JDBCDatabase that will work like any other database, e.g. OracleDatabase, in jOOQ-meta. The reason why I haven't implemented this yet, is because I'm exploring more generic data sources for jOOQ-meta (e.g. XML files), from which code can be generated. This is due for jOOQ 3.0 > What is the use of the console? Can i use it simply by starting the > responsible jar file? There is a section in the manual explaining how the jOOQ Console works: http://www.jooq.org/doc/2.6/manual/tools/jooq-console/ > When we develop code for the dialect and code generator is that supposed to > be hosted in your repository? You have several options: 1) Fork jOOQ under the terms of the ASL 2.0 and maintain (and possibly publish) your own extension. This means you have more liberty, but no maintenance support from my side, except for inquiries on this list. You will then have to merge jOOQ updates into your fork. If you want, I can link to your fork from the jOOQ website. 2) Contribute to jOOQ under the terms of the ASL 2.0 and share the copyright with me (for jOOQ-meta contributions). This means that we share maintenance work. This is also the model under which the jOOQ Console is published. 3) Contribute to jOOQ under the terms of the ASL 2.0 and contribute the copyright to me. This means that I will do most of the maintenance work. This is the model under which DB2, HSQLDB, H2, and Sybase SQL Anywhere integrations were contributed. Case 1) is straightforward. In cases 2) and 3) we can further discuss the terms of cooperation. I'm open to suggestions. > I didnt see the jooq-test project/package in the jooq-2.6.0-full.zip from > sourceforge. > Is that project only available from git repository? Yes, unfortunately, jOOQ-test is not yet a maven module allowing to run tests without manual intervention. The best way is to clone GitHub master and work directly on the source code. Cheers Lukas
