Manuals, Documentation, Tutorials
|3.2||HTML||HTML HTML (multi-page) PDF|
|3.1||HTML||HTML HTML (multi-page) PDF|
|3.0||HTML||HTML HTML (multi-page) PDF||
|2.6||HTML||HTML HTML (multi-page) PDF|
|2.5||HTML||HTML HTML (multi-page) PDF|
Getting started with the tutorial
Your simplest entry point is probably to get the tutorial running. It shows how to use jOOQ and its code generator with a simple MySQL database
Before you go on and read the whole manual, there are a couple of interesting questions that you might want to consider:
Q: When I generate source code from MySQL, can I also use it on another database?
A: Yes! The generated Java code will work for all supported databases, not only for the database driver that you used when you generated the code.
Q: When I generate source code from my developer database, can I also use it on production?
A: Yes! You can map your schema at code generation time or at run time. See the manual for details.
Q: Can I use jOOQ without code generation?
A: Yes! You can define tables, fields, conditions using Strings. See the manual for details.
Q: Can I use jOOQ as a query builder and execute queries with Spring?
A: Yes! This has been done by other users and will be documented soon. See this Stack Overflow question for details.
Q: Does jOOQ manage transactions?
A: No, it doesn't and that's good! There are so many competing transaction models, jOOQ wouldn't choose the right one for you. See this Stack Overflow question for details.
Q: Does jOOQ support MongoDB?
A: No, jOOQ wouldn't be so good at modelling SQL in Java, if NoSQL elements had to be supported in the API. In return, our engineers have become SQL and JDBC pros.
jOOQ is about SQL. We recommend you also read these excellent resources, which talk about SQL in general:
|Markus Winand is the author of the popular website Use-The-Index-Luke.com. His book explains nicely how to achieve proper indexing and performance in popular RDBMS:
|Bill Karwin has helped thousands of people write better SQL and build stronger relational databases. Now he’s sharing his collection of antipatterns—the most common errors he’s identified in those thousands of requests for help: