public Interface InsertQuery<R extends org.jooq.Record>

Redeclares org.jooq.ConditionProvider.addConditions.

Adds a new condition to the query, connecting it to existing conditions with Operator#AND.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

condition:Condition

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.ConditionProvider.addConditions.

Adds new conditions to the query, connecting them to existing conditions with Operator#AND.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

conditions:Condition[]

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.ConditionProvider.addConditions.

Adds new conditions to the query, connecting them to existing conditions with Operator#AND.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

conditions:Collection<? extends Condition>

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.ConditionProvider.addConditions.

Adds a new condition to the query, connecting it to existing conditions with the provided operator.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

condition:Condition

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.ConditionProvider.addConditions.

Adds new conditions to the query, connecting them to existing conditions with the provided operator.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

conditions:Condition[]

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.ConditionProvider.addConditions.

Adds new conditions to the query, connecting them to existing conditions with the provided operator.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

conditions:Collection<? extends Condition>

The condition

Annotations

@Override

@Support:CUBRID, DERBY, H2, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Short for calling newRecord(); setRecord(record);

Parameters

record:R

The record to add to this insert statement.

Annotations

@Support

Add a value to the ON DUPLICATE KEY UPDATE clause of this INSERT statement, where this is supported.

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Add a value to the ON DUPLICATE KEY UPDATE clause of this INSERT statement, where this is supported.

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Add multiple values to the ON DUPLICATE KEY UPDATE clause of this INSERT statement, where this is supported.

Please assure that key/value pairs have matching <T> types. Values can either be of type <T> or Field<T>

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Redeclares org.jooq.StoreQuery.getReturnedRecord.

Doc from org.jooq.StoreQuery.getReturnedRecord.

The record holding returned values as specified by any of the setReturning() methods.

If the insert statement returns several records, this is the same as calling getReturnedRecords().get(0)

This implemented differently for every dialect:

• Firebird and Postgres have native support for INSERT … RETURNING and UPDATE … RETURNING clauses
• HSQLDB, Oracle, and DB2 JDBC drivers allow for retrieving any table column as "generated key" in one statement
• Derby, H2, Ingres, MySQL, SQL Server only allow for retrieving IDENTITY column values as "generated key". If other fields are requested, a second statement is issued. Client code must assure transactional integrity between the two statements.
• Sybase and SQLite allow for retrieving IDENTITY values as @@identity or last_inserted_rowid() values. Those values are fetched in a separate SELECT statement. If other fields are requested, a second statement is issued. Client code must assure transactional integrity between the two statements.

This feature works with INSERT statements for all SQL dialects

Returns:R

The returned value as specified by any of the setReturning() methods. This may return null in case jOOQ could not retrieve any generated keys from the JDBC driver.

Annotations

@Override

@Nullable

@Support

Redeclares org.jooq.StoreQuery.getReturnedRecords.

Doc from org.jooq.StoreQuery.getReturnedRecords.

The records holding returned values as specified by any of the setReturning() methods.

This implemented differently for every dialect:

• Firebird and Postgres have native support for INSERT … RETURNING and UPDATE … RETURNING clauses
• HSQLDB, Oracle, and DB2 JDBC drivers allow for retrieving any table column as "generated key" in one statement
• Derby, H2, Ingres, MySQL, SQL Server only allow for retrieving IDENTITY column values as "generated key". If other fields are requested, a second statement is issued. Client code must assure transactional integrity between the two statements.
• Sybase and SQLite allow for retrieving IDENTITY values as @@identity or last_inserted_rowid() values. Those values are fetched in a separate SELECT statement. If other fields are requested, a second statement is issued. Client code must assure transactional integrity between the two statements.

[#5070] Due to an early API design flaw, this method historically returns the type R, not a more generic type Record. This means that only actual columns in R can be returned. For a more generic set of column expressions, use getResult() instead.

This feature works with INSERT statements for all SQL dialects

Returns:@NotNull Result<R>

The returned values as specified by any of the setReturning() methods. Note:

• Not all databases / JDBC drivers support returning several values on multi-row inserts!
• This may return an empty Result in case jOOQ could not retrieve any generated keys from the JDBC driver.

Annotations

@Override

@NotNull

@Support

Adds a new Record to the insert statement for multi-record inserts

Calling this method will cause subsequent calls to addValue(Field, Object) (and similar) to fill the next record.

If this call is not followed by addValue(Field, Object) calls, then this call has no effect.

If this call is done on a fresh insert statement (without any values yet), then this call has no effect either.

Annotations

@Support

Whether a ON CONFLICT clause should be added to this INSERT statement.

When setting this flag to true, be sure to also add values "for update" using the addValueForUpdate(Field, Field) methods.

Annotations

@Support

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Whether a ON CONFLICT clause should be added to this INSERT statement.

When setting this flag to true, be sure to also add values "for update" using the addValueForUpdate(Field, Field) methods.

Annotations

@Support

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Whether use a ON CONFLICT or ON CONFLICT ON CONSTRAINT clause in this INSERT statement.

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, YUGABYTEDB

Whether use a ON CONFLICT or ON CONFLICT ON CONSTRAINT clause in this INSERT statement.

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, YUGABYTEDB

Whether use a ON CONFLICT or ON CONFLICT ON CONSTRAINT clause in this INSERT statement.

Annotations

@Support

Adds a new condition the onConflict(Field...) clause.

This is for use with SQLDialect#POSTGRES's onConflict(Field...) clause.

Parameters

condition:Condition

The condition

Annotations

@Support:POSTGRES, SQLITE, YUGABYTEDB

Whether an ON DUPLICATE KEY IGNORE clause should be added to this INSERT statement.

This clause is not actually supported in this form by any database, but can be emulated as such:

INSERT IGNORE INTO …

INSERT INTO … ON CONFLICT DO NOTHING

MERGE INTO [dst]
USING ([values])
ON [dst.key] = [values.key]
WHEN NOT MATCHED THEN INSERT ..

INSERT INTO [dst] ( ... )
SELECT [values]
WHERE NOT EXISTS (
  SELECT 1
  FROM [dst]
  WHERE [dst.key] = [values.key]
)

The ON DUPLICATE KEY UPDATE flag is mutually exclusive with the ON DUPLICATE KEY IGNORE flag (see onDuplicateKeyIgnore(boolean). Setting one will unset the other

Annotations

@Support

Whether a ON DUPLICATE KEY UPDATE clause should be added to this INSERT statement.

When setting this flag to true, be sure to also add values "for update" using the addValueForUpdate(Field, Field) methods.

The ON DUPLICATE KEY UPDATE flag is mutually exclusive with the ON DUPLICATE KEY IGNORE flag (see onDuplicateKeyIgnore(boolean). Setting one will unset the other

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

See Also

InsertOnDuplicateStep#onDuplicateKeyUpdate()

Set an empty record with the DEFAULT VALUES clause.

Annotations

@Support:CUBRID, DERBY, FIREBIRD, H2, HSQLDB, MARIADB, MYSQL, POSTGRES, SQLITE, YUGABYTEDB

Redeclares org.jooq.StoreQuery.setReturning.

Doc from org.jooq.StoreQuery.setReturning.

Configure the INSERT or UPDATE statement to return all fields in R.

This feature works with INSERT statements for all SQL dialects

Annotations

@Override

@Support

Redeclares org.jooq.StoreQuery.setReturning.

Doc from org.jooq.StoreQuery.setReturning.

Configure the INSERT or UPDATE statement to return the generated identity value.

This feature works with INSERT statements for all SQL dialects

Parameters

identity:Identity<R, ?>

The table's identity

Annotations

@Override

@Support

Redeclares org.jooq.StoreQuery.setReturning.

Doc from org.jooq.StoreQuery.setReturning.

Configure the INSERT or UPDATE statement to return a list of fields in R.

This feature works with INSERT statements for all SQL dialects

Parameters

fields:SelectFieldOrAsterisk[]

Fields to be returned

Annotations

@Override

@Support

Redeclares org.jooq.StoreQuery.setReturning.

Doc from org.jooq.StoreQuery.setReturning.

Configure the INSERT or UPDATE statement to return a list of fields in R.

This feature works with INSERT statements for all SQL dialects

Parameters

fields:Collection<? extends SelectFieldOrAsterisk>

Fields to be returned

Annotations

@Override

@Support

Use a SELECT statement as the source of values for the INSERT statement.

Annotations

@Support

Use a SELECT statement as the source of values for the INSERT statement.

Annotations

@Support