TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

Forge SQL Optimistic Locking

1 post · Jul 2025

What this trail covers

Forge SQL now supports optimistic locking for reliable data storage in concurrent update scenarios. This feature addresses race conditions by using a versioning mechanism (either updated_at timestamp or an integer version) to ensure that updates are only applied if the data has not been modified since it was last read. This is particularly useful in Forge SQL's constraint of single query per .query() call, enabling robust data integrity without traditional transactions.

All Atlassian trails
  1. Reliable Data Storage Using Optimistic Locking in Forge SQLThis post details the implementation of optimistic locking in Atlassian Forge using Forge SQL, specifically for a release readiness checklist example. It explains the problem of race conditions in concurrent updates and presents optimistic locking as a solution compatible with Forge SQL's single-query constraint. The post covers schema design using `updated_at` (DATETIME) or `version` (INTEGER) as version fields, the optimistic locking flow with backend/frontend interactions, and options for handling conflicts (error message, returning both versions, auto-merge). It also provides instructions for running a Drizzle ORM-based example implementation.