SQL statements and features
Feature	ASE	DB2	Derby	H2	HSQLDB	Ingres	MySQL	Oracle	Postgres	SQLite	SQL Server	Sybase
INSERT with VALUES	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
INSERT with VALUES (multiple records)	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
INSERT with SELECT	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
INSERT with ON DUPLICATE KEY UPDATE	no	yes [1]	no	no	yes [1]	no	yes	yes [1]	no	no	yes [1]	yes [1]
INSERT with RETURNING	partially [3]	yes [4]	partially [3]	partially [3]	yes [4]	partially [3]	yes [3]	partially [4]	yes	partially [2]	partially [3]	partially [2]
SELECT	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
SELECT with CONNECT BY	no	no	no	no	no	no	no	yes	no	no	no	no
SELECT with LIMIT .. OFFSET	partially [7]	yes [8]	yes [9]	yes [10]	yes [10]	yes [9]	yes [10]	yes [11]	yes [10]	yes [10]	yes [8]	yes [12]
SELECT with FOR UPDATE	yes	yes	yes	yes	yes	yes	yes	yes	yes	no	no	yes
SELECT with FOR UPDATE OF (field-list)	no	yes	yes	yes	yes	yes	no	yes	no	no	no	yes
SELECT with FOR UPDATE OF (table-list)	no	yes [13]	yes [13]	yes	yes	yes [13]	no	yes [13]	yes	no	no	yes
SELECT with FOR UPDATE WAIT, NOWAIT, SKIP LOCKED	no	no	no	no	no	no	no	yes	no	no	no	no
UPDATE	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
DELETE	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
MERGE	no	yes	no	no [6]	yes	no	no	yes	no	no	yes	yes
MERGE (Oracle extensions)	no	no	no	no	no	no	no	yes	no	no	no	no
TRUNCATE	yes	yes	yes	yes	yes	yes [14]	yes	yes	yes	yes [14]	yes	yes
Sequence CURRVAL	no	yes	no	yes	no	yes	no	yes	yes	no	no	yes
Sequence NEXTVAL	no	yes	yes	yes	yes	yes	no	yes	yes	no	no	yes
JDBC features
Feature	ASE	DB2	Derby	H2	HSQLDB	Ingres	MySQL	Oracle	Postgres	SQLite	SQL Server	Sybase
batch operations	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes	yes
jOOQ features
Feature	ASE	DB2	Derby	H2	HSQLDB	Ingres	MySQL	Oracle	Postgres	SQLite	SQL Server	Sybase
CSV Data loader	yes [5]	yes	yes [5]	yes [5]	yes	yes [5]	yes	yes	yes [5]	yes [5]	yes	yes
Functions
Feature	ASE	DB2	Derby	H2	HSQLDB	Ingres	MySQL	Oracle	Postgres	SQLite	SQL Server	Sybase
Last inserted ID	yes	no	yes	yes	yes	yes	yes	no	no	yes	yes	yes

• [1] MySQL's INSERT .. ON DUPLICATE KEY UPDATE statement is simulated using an equivalent MERGE statement
• [2] Postgres' INSERT .. RETURNING statement is simulated by fetching the last inserted ID explicitly with a new statement. Other fields than the ID are fetched with another statement. Client code must ensure transactional integrity between the three statements to prevent race conditions (e.g. set autocommit to off). This does not work for multi-record inserts.
• [3] Postgres' INSERT .. RETURNING statement is simulated by using JDBC's PreparedStatement.getGeneratedKeys() functionality. Other fields than the ID are fetched with another statement. Client code must ensure transactional integrity between the two statements to prevent race conditions (e.g. set autocommit to off). This may not work for multi-record inserts in some dialects
• [4] Postgres' INSERT .. RETURNING statement is simulated by using JDBC's PreparedStatement.getGeneratedKeys() functionality. All fields can be fetched in a single statement. This may not work for multi-record inserts in some dialects
• [5] The loader API has an option to use MySQL's INSERT .. ON DUPLICATE KEY UPDATE statement, which only works in some dialects. See also [1]
• [6] H2's MERGE statement is quite different from the SQL:2003 standard MERGE statement. It is currently not supported by jOOQ
• [7] Sybase ASE has no means of specifying an OFFSET like other dialects. LIMIT is translated to the TOP clause
• [8] DB2 knows a FIRST ROWS clause without OFFSET. SQL Server knows a TOP clause without OFFSET. LIMIT .. OFFSET is simulated using nested SELECT and filtering on ROW_NUMBER() OVER()
• [9] Derby knows the OFFSET .. ROWS FETCH NEXT .. ROWS ONLY clause, Ingres has a similar OFFSET .. ROWS FETCH NEXT .. ROWS ONLY clause. They work just the same as [10]
• [10] Many databases know the LIMIT .. OFFSET clause as declared in the jOOQ API
• [11] Oracle has no native support for LIMIT .. OFFSET clauses. Instead, LIMIT .. OFFSET is simulated using nested SELECT and filtering on ROW_NUMBER() OVER()
• [12] Sybase knows a TOP .. START AT .. clause that works just the same as [10]
• [13] Some databases do not support a FOR UPDATE OF (table-list) clause. But jOOQ knows all columns in generated tables, hence jOOQ renders an appropriate FOR UPDATE OF (field-list) clause instead
• [14] Some databases do not support a TRUNCATE statement. An equivalent DELETE statement is issued instead.