I have to say this is a stunning project. My background is that of working with SQL based data stores (for far too many years) and system server design means I think in 'SQL' first, overall system performance second and coding only third.
The result is that over the last few years I've had to deal with a growing number of programmers who think that the queries coming out of convoluted ORMs or LINQ like based systems are some how a problem for the DBA or hardware tech team to resolve, without any real proof that the programmers could use better solutions for at least part of their development. In the last few months this has become even more an issue for me as I've changed roles in live so need to spend far more time focussed on coding than I have done. At the start of this peirod I ended up looking at ORMs (depressing to say the least) and then ended up looking at Empire-DB (better, but...), I'm happy to say that having now found jOOQ I'm starting to be a little more productive than I was as I can express at code level what I wish to happen at the database level, with all the major plumbing work handed by the code generator. Also the level of documentation is great for someone starting at the begining - many other solutions seem to be written by experts for other experts, so far the only thing I would ask is for 2 minor issues to be fixed in the docs at some point so others do not get slowed down when they first start. 1) http://www.jooq.org/tutorial.php#step3 The example code includes import static test.generated.Tables.* This seems to be wrong with 2.6 as the import point is the package rather than a class with static entries. 2) http://www.jooq.org/doc/2.6/manual/code-generation/codegen-configuration/ The image showing the Referenced Libraries needed to set up Eclipse is out of date as the jars are now version stamped and jooq-meta-2.6.0.jar needs to be included Both of the above slowed me down when first trying to eval jOOQ as I needed to extend my understanding of the product before I could follow the basic examples. Also with the speed at which jOOQ is evolving can I suggest that the whole community starts to add a comment in any example code that they post to indicate which release of jOOQ the example is for. There are many well thought out examples posted on blogs across the internet, but many will not work with the current release and so again slow the process of doing an eval. Thanks for all the work done. Roger
