www.jooq.org Open in urlscan Pro
84.16.84.89  Public Scan

Form analysis
3 forms found in the DOM

Name: registration-email — POST #

<form id="registration-email-form" name="registration-email" class="registration-email-form" action="#" method="POST">
  <div class="reg-row">
    <div class="reg-col reg-col-1">Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">E-Mail</div>
    <div class="reg-col reg-col-2"><input class="input" name="email" type="email"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Phone number</div>
    <div class="reg-col reg-col-2"><input class="input" name="phone" type="tel"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Company Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="company_name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1"> Anything else you'd like to tell us?<br> How did you hear from jOOQ?<br> What made you try jOOQ?<br> What are your expectations? </div>
    <div class="reg-col reg-col-2"><textarea name="comments"></textarea></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">&nbsp;</div>
    <div class="reg-col reg-col-1">
      <button class="save"> Save </button>
    </div>
    <!--
    <div class="reg-col reg-col-1">
        <button class="no-thanks" data-cookie="jooq-registration-email" data-fade="email">
            No thanks
        </button>    
    </div>
	-->
  </div>
  <input type="hidden" id="registered-by" name="registered-by" value="newsletter-popup">
</form>

Name: registration-email — POST #

<form id="registration-email-form" name="registration-email" class="registration-email-form" action="#" method="POST">
  <div class="reg-row">
    <div class="reg-col reg-col-1">Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">E-Mail</div>
    <div class="reg-col reg-col-2"><input class="input" name="email" type="email"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Phone number</div>
    <div class="reg-col reg-col-2"><input class="input" name="phone" type="tel"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Company Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="company_name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1"> Anything else you'd like to tell us?<br> How did you hear from jOOQ?<br> What made you try jOOQ?<br> What are your expectations? </div>
    <div class="reg-col reg-col-2"><textarea name="comments"></textarea></div>
  </div>
  <input type="hidden" id="registered-by" name="registered-by" value="oss-license">
</form>

Name: registration-email — POST #

<form id="registration-email-form" name="registration-email" class="registration-email-form" action="#" method="POST">
  <div class="reg-row">
    <div class="reg-col reg-col-1">Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">E-Mail</div>
    <div class="reg-col reg-col-2"><input class="input" name="email" type="email"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Phone number</div>
    <div class="reg-col reg-col-2"><input class="input" name="phone" type="tel"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1">Company Name</div>
    <div class="reg-col reg-col-2"><input class="input" name="company_name"></div>
  </div>
  <div class="reg-row">
    <div class="reg-col reg-col-1"> Anything else you'd like to tell us?<br> How did you hear from jOOQ?<br> What made you try jOOQ?<br> What are your expectations? </div>
    <div class="reg-col reg-col-2"><textarea name="comments"></textarea></div>
  </div>
  <input type="hidden" id="registered-by" name="registered-by" value="trial-license">
</form>

Text Content

 * Learn
 * Download / Pricing
 * Blog

All information from this page will be kept strictly confidential


TELL US A LITTLE BIT ABOUT YOURSELF AND JOIN OUR NEWSLETTER (EXAMPLES)



Name

E-Mail

Phone number

Company Name

Anything else you'd like to tell us?
How did you hear from jOOQ?
What made you try jOOQ?
What are your expectations?

 
Save


JOOQ GENERATES JAVA CODE FROM YOUR DATABASE AND LETS YOU BUILD TYPE SAFE SQL
QUERIES THROUGH ITS FLUENT API.

Start your free jOOQ trial now!


GREAT REASONS FOR USING JOOQ

Our customers spend most time on their business-logic.
Because jOOQ takes care of all their Java/SQL infrastructure problems.


DATABASE FIRST

Tired of ORMs driving your database model?

Whether you design a new application or integrate with your legacy, your
database holds your most important asset: your data.

jOOQ is SQL-centric. Your database comes "first".


TYPESAFE SQL

Fed up with detecting SQL syntax errors in production?

SQL is a highly expressive and type safe language with a rich syntax. jOOQ
models SQL as an internal DSL and uses the Java compiler to compile your SQL
syntax, metadata and data types.


CODE GENERATION

Bored with renaming table and column names in your Java code?

jOOQ generates Java classes from your database metadata. Your Java compiler will
tell you when your code is out of sync with your schema.


ACTIVE RECORDS

Annoyed by the amount of SQL you write for CRUD?

jOOQ lets you perform CRUD and POJO mapping directly on Active Records, which
are also generated from the code generator.


MULTI-TENANCY

Worried about multi-schema or shared-schema multi-tenancy?

jOOQ lets you configure database schema and table overrides at runtime and also
supports row-level security.


STANDARDISATION

Overwhelmed by the subtle differences in SQL dialects?

jOOQ performs SQL transformation to transform common SQL expressions into your
database's closest match. Write SQL that works on all your databases.


QUERY LIFECYCLE

Irritated by your ORM's mysterious SQL generation?

jOOQ lets you hook into its SQL generation lifecycle, for logging, transaction
handling, ID generation, SQL transformation and much more.


PROCEDURES

Surprised by your ORM's lack of support for stored procedures?

Stored Procedures are an essential feature of modern SQL databases. jOOQ lets
you embed stored function calls into your SQL statements.


DATABASE FIRST

Your data is your most important asset.

You have made a well-informed decision, when you chose a relational database
management system to store your data. You are used to writing SQL to query and
manipulate your data. Now, you're looking for a professional tool to help you
write your SQL in Java.

With jOOQ, your database and your data come first. You want to be able to use
every feature your database offers, using the language that is used to interact
with databases: SQL. jOOQ will let you do precisely that.

More details can be seen in the manual:

 * jOOQ's mission statement
 * Different use cases for jOOQ




TYPESAFE SQL

SQL is a very unique and rich language, optimally designed to express complex
queries in a simple, declarative form. When writing SQL, you will focus on what
data you want to fetch, not how you want to fetch it.

jOOQ treats SQL like what it is in the first place: A language. Through its
unique and modern fluent API design techniques, jOOQ embeds SQL as an internal
domain-specific language directly in Java, making it easy for developers to
write and read code that almost feels like actual SQL.

As an internal domain-specific language, jOOQ can leverage the powerful Java
compiler and Java's generics for

 * Column type checks
 * Row value expression type checks
 * SQL syntax checks

More details can be seen in the manual:

 * jOOQ's DSL and model APIs
 * Lexical and logical SQL clause ordering




CODE GENERATION

SQL meta data is an essential part of your code base. It is where you define
table and column types, which can be used in your SQL statements in a type safe
manner.

During development, SQL meta data are in constant flux. Developers add, rename,
remove tables, columns, procedures, parameters all the time.

Using jOOQ's code generator, your Java code will not only compile against your
actual SQL meta data, it will also immediately take notice of the changes
performed to SQL meta data. This will help prevent syntax errors due to
improperly changed meta data in an early phase of your development or deployment
cycle.

No more productive surprises due to changed meta data!

More details can be seen in the manual:

 * Using jOOQ with the code generator
 * The section about code generation




ACTIVE RECORDS

Much of your daily work with SQL is repetitive CRUD: Creating, Reading,
Updating, Deleting of database records.

jOOQ incorporates the popular Active Record paradigm by modelling each database
table as a typesafe record, which is capable of storing, deleting and refreshing
itself through an intuitive API.

Apart from the above operations, jOOQ's Active Records are also capable of

 * Optimistic locking
 * Foreign key navigation
 * Mapping themselves from / to your custom POJO types

More details can be seen in the manual:

 * Weakly and strongly typed records
 * CRUD with jOOQ




MULTI-TENANCY

You have established a well-defined development process. You're probably using

 * Development databases (maybe even one per developer)
 * Test databases
 * Staging databases
 * Production databases

jOOQ lets you configure your environment easily, allowing you to rewrite
generated SQL schema and table names.

More details can be seen in the manual:

 * Schema and table rewriting at code-generation time
 * Schema and table rewriting at runtime




STANDARDISATION

Each SQL dialect is different in various obvious and subtle ways. These
differences include things like:

 * SQL statements (e.g. MERGE vs. ON DUPLICATE KEY UPDATE)
 * SQL clauses (e.g. Oracle CONNECT BY vs. hierarchical CTE)
 * Built-in functions (e.g. NVL, COALESCE, IFNULL, CASE .. END)
 * Pseudo elements (e.g. DUAL, SYS.DUMMY, SYSIBM.DUAL, ...)
 * Syntax elements (e.g. derived column lists)

Popular SQL database vendors have put a lot of effort into their most innovative
and useful SQL clauses and functions and with jOOQ, you can use them very
easily.

jOOQ produces an AST from your queries, which can be transformed into equivalent
SQL expressions, should you chose a syntax element, which is not natively
supported by your database.

More details can be seen in the manual:

 * SQL Dialect management
 * Standardising LIMIT, OFFSET, TOP




QUERY LIFECYCLE

The Java to SQL integration is at the core of your business. It interfaces your
two most important assets:

 * Your data
 * Your business logic

You want to stay in full control of this interface, influencing SQL rendering,
variable binding, query execution and other query operation lifecycles.

jOOQ provides you with a rich SPI to inject custom behaviour, in order to
manage:

 * Custom logging
 * Transaction management
 * Event triggers
 * SQL transformation

More details can be seen in the manual:

 * Manual sections about ExecuteListeners
 * Javadoc sections about ExecuteListeners




PROCEDURES

More and more SQL databases implement some sort of procedural language for
in-database data processing and bulk operations. You may even chose to move
critical business logic into the database for performance, security or other
reasons.

With jOOQ, stored procedures and stored functions are first-class citizens, if
you chose them to be. The jOOQ code generator will generate a callable method
for every routine. Stored functions can be embedded typesafely into your SQL
statements.

More details can be seen in the manual:

 * Stored procedures and functions in jOOQ
 * Generated artefacts from stored procedures and functions




SOME OF OUR CUSTOMERS




More customers


TESTIMONIALS

Thousands of happy jOOQ users aren't just using jOOQ. They love jOOQ.
With jOOQ, writing SQL in Java is fun and productive. Here's what some of our
users say:



Using jOOQ has been a joy, it's made life much easier for us.

Ilkka Halila - Boomlagoon Ltd.



The level of support from the jOOQ team was nothing short of excellent. They
were extremely easy to talk to, and had my problem solved in less than an hour
on Skype. I would recommend jOOQ support services to anyone.

Paul Woodland - ABC Information Solutions Pty Ltd





Thanks to jOOQ we are in control of our SQL which helps to be in control of our
project.

Marco Dubacher - Ergon Informatik AG



The ability to trivially add SQL functions in a single line of a single method
is fantastic! Honestly, we’ve gotten away using your documentation, examples,
and source and never had to bug you guys with “How do I …?” You blog, manual,
etc, all combine together with a simple library to make a great product that
let’s us do some insane SQL *really really easily*.

Daniel Owens - DanielSecurities





We successfully deploy jOOQ in a range of projects with clients from various
sectors, such as construction companies, telecom or security services companies:
jOOQ offers us the necessary flexibility to satisfy their different
requirements.

Gabrio Rivera - OneOverZero GmbH


EXAMPLES

With the jOOQ DSL, SQL looks almost as if it were natively supported by Java.

SELECT TITLE
FROM BOOK
WHERE BOOK.PUBLISHED_IN = 2011
ORDER BY BOOK.TITLE

create.select(BOOK.TITLE)
      .from(BOOK)
      .where(BOOK.PUBLISHED_IN.eq(2011))
      .orderBy(BOOK.TITLE)

jOOQ also supports more complex SQL statements. get all authors' first and last
names, and the number of books they've written in German, if they have written
more than five books in German in the last three years (from 2011), and sort
those authors by last names limiting results to the second and third row

SELECT AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME, COUNT(*)
FROM AUTHOR
JOIN BOOK ON AUTHOR.ID = BOOK.AUTHOR_ID
WHERE BOOK.LANGUAGE = 'DE'
AND BOOK.PUBLISHED > DATE '2008-01-01'
GROUP BY AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME
HAVING COUNT(*) > 5
ORDER BY AUTHOR.LAST_NAME ASC NULLS FIRST
LIMIT 2
OFFSET 1

create.select(AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME, count())
      .from(AUTHOR)
      .join(BOOK).on(AUTHOR.ID.equal(BOOK.AUTHOR_ID))
      .where(BOOK.LANGUAGE.eq("DE"))
      .and(BOOK.PUBLISHED.gt(date("2008-01-01")))
      .groupBy(AUTHOR.FIRST_NAME, AUTHOR.LAST_NAME)
      .having(count().gt(5))
      .orderBy(AUTHOR.LAST_NAME.asc().nullsFirst())
      .limit(2)
      .offset(1)


TYPESAFETY EXAMPLES

SQL is a very type safe language. So is jOOQ. jOOQ uniquely respects SQL's row
value expression typesafety. jOOQ will use your Java compiler to type-check the
following:


PREDICATES

jOOQ type-checks simple comparison predicates and predicates with subqueries.

select().from(t).where(t.a.eq(select(t2.x).from(t2));
// Type-check here: ---------------> ^^^^
select().from(t).where(t.a.eq(any(select(t2.x).from(t2)));
// Type-check here: -------------------> ^^^^
select().from(t).where(t.a.in(select(t2.x).from(t2));
// Type-check here: ---------------> ^^^^


SET OPERATIONS

jOOQ type-checks degree and data types of union subselects.

select(t1.a).from(t1).unionAll(select(t2.a).from(t2));
// Type-check here: ----------------> ^^^^
select(t1.a, t1.b).from(t1).union(select(t2.a, t2.b).from(t2));
// Type-check here: -------------------> ^^^^^^^^^^

Some more sophisticated examples show type-checks on row value expressions:

SELECT * FROM t WHERE (t.a, t.b) = (1, 2)

SELECT * FROM t WHERE (t.a, t.b) OVERLAPS (date1, date2)

SELECT * FROM t WHERE (t.a, t.b) IN (SELECT x, y)

UPDATE t SET (a, b) = (SELECT x, y FROM t2 WHERE ...)

INSERT INTO t (a, b) VALUES (1, 2)
 

select().from(t).where(row(t.a, t.b).eq(1, 2));
// Type-check here: ----------------->  ^^^^
select().from(t).where(row(t.a, t.b).overlaps(date1, date2));
// Type-check here: ------------------------> ^^^^^^^^^^^^
select().from(t).where(row(t.a, t.b).in(select(t2.x, t2.y)));
// Type-check here: -------------------------> ^^^^^^^^^^
update(t).set(row(t.a, t.b), select(t2.x, t2.y).where(...));
// Type-check here: --------------> ^^^^^^^^^^
insertInto(t, t.a, t.b).values(1, 2);
// Type-check here: ---------> ^^^^


DOWNLOAD

Start your free jOOQ trial now!



↑ Back to top


COMMUNITY

 * Our customers
 * Tech Blog
 * Business Blog
 * GitHub
 * Stack Overflow
 * Activities
 * jOOQ Tuesdays


SUPPORT

 * User Groups
 * Reddit /r/jOOQ
 * Trainings
 * Contact
 * Bluesnap Account Login


LEGAL

 * Licenses
 * Privacy Policy
 * Terms of Service
 * Contributor Agreement


DOCUMENTATION

 * FAQ
 * Tutorial
 * The manual (single page)
 * The manual (multi page)
 * The manual (PDF)
 * Javadoc
 * Using SQL in Java is simple!
 * Convince your manager!
 * Our other products
 * Translate SQL between databases
 * Generate a diff between schemas
 * How to pronounce jOOQ

© 2009 - 2024 by Data Geekery™ GmbH. All rights reserved.
jOOQ™ is a trademark of Data Geekery GmbH. All other trademarks and copyrights
are the property of their respective owners.


REGISTRATION (OPTIONAL)

Name

E-Mail

Phone number

Company Name

Anything else you'd like to tell us?
How did you hear from jOOQ?
What made you try jOOQ?
What are your expectations?



LICENSE AGREEMENT

By downloading the jOOQ Community Edition, you confirm to have read and that you
agree to the terms of the Apache Software License 2.0.

I do not agree I agree


REGISTRATION (OPTIONAL)

Name

E-Mail

Phone number

Company Name

Anything else you'd like to tell us?
How did you hear from jOOQ?
What made you try jOOQ?
What are your expectations?



OTHER DISTRIBUTIONS

The free trial supports Java 8. If you would like to try the jOOQ for Java 11 or
Java 17 distributions, please use the downloads from /download/versions or
contact sales@datageekery.com.


LICENSE AGREEMENT

By downloading a 30 day trial license for the jOOQ Professional Edition or the
jOOQ Enterprise Edition, you confirm to have read and that you agree to the
terms of the jOOQ License.

I do not agree I agree


LICENSE AGREEMENT

By purchasing the jOOQ Express Edition, the Professional Edition, or the jOOQ
Enterprise Edition, you confirm to have read and that you agree to the terms of
the jOOQ License

If you prefer to purchase jOOQ Enterprise Edition licenses by purchase order /
invoice, please contact sales@datageekery.com or one of our preferred resellers
to get a quote.

I do not agree I agree
Sign up for our newsletter Maybe later

Help