Обычной !

UPDATE TABLE SET ...

Best regards,
Dnico.

Так это же связано только с блокировкой ...

автор(1.5) Explicit locking
Nickolay Samofatov
The addition of the optional WITH LOCK clause provides a limited explicit pessimistic locking capability
for cautious use in conditions where the affected row set is a) extremely small (ideally, a singleton)
and b) precisely controlled by the application code.
NOTE The need for a pessimistic lock in Firebird is very rare indeed and should be well understood
before use of this extension is considered.
Syntax
SELECT ... FROM <sometable>
[WHERE ...]
[FOR UPDATE [OF ...]]
[WITH LOCK]
...;
If the WITH LOCK clause succeeds, it will secure a lock on the selected rows and prevent any other
transaction from obtaining write access to any of those rows, or their dependants, until your
transaction ends.
If the FOR UPDATE clause is included, the lock will be applied to each row, one by one, as it is fetched
into the server-side row cache. It becomes possible, then, that a lock which appeared to succeed
when requested will nevertheless fail subsequently, when an attempt is made to fetch a row which
becomes locked by another transaction.


Best regards,
Dnico.