The jOOQ User Manual SQL execution CRUD with UpdatableRecords Simple CRUD CRUD: Store

previous : next

CRUD: Store

Supported by ✅ Open Source Edition   ✅ Express Edition   ✅ Professional Edition   ✅ Enterprise Edition

Storing an org.jooq.UpdatableRecord will perform a INSERT or an UPDATE operation on the record. In general, new records are always inserted, whereas records fetched from the database are always updated.

This is best visualised in code:

// Create a new record
BookRecord book1 = create.newRecord(BOOK);

// Insert the record: INSERT INTO BOOK (TITLE) VALUES ('1984');
book1.setTitle("1984");
book1.store();

// Update the record: UPDATE BOOK SET PUBLISHED_IN = 1984 WHERE ID = :id
book1.setPublishedIn(1948);
book1.store();

// Get the (possibly) auto-generated ID from the record
Integer id = book1.getId();

// Get another instance of the same book
BookRecord book2 = create.fetchOne(BOOK, BOOK.ID.eq(id));

// Update the record: UPDATE BOOK SET TITLE = 'Animal Farm' WHERE ID = :id
book2.setTitle("Animal Farm");
book2.store();

Some remarks about storing:

• jOOQ sets only modified values in INSERT statements or UPDATE statements. This allows for default values to be applied to inserted records, as specified in CREATE TABLE DDL statements.
• When store() performs an INSERT statement, jOOQ attempts to load any generated keys from the database back into the record. For more details, see the manual's section about IDENTITY values.
• In addition to loading identity values, store() can also be configured to refresh the entire record. See the returnAllOnUpdatableRecord setting for details
• When loading records from POJOs, jOOQ will assume the record is a new record. It will hence attempt to INSERT it.
• When you activate optimistic locking, storing a record may fail, if the underlying database record has been changed in the mean time.

The jOOQ User Manual SQL execution CRUD with UpdatableRecords Simple CRUD CRUD: Store

previous : next