> No. The feature is intended to support deadlock-free transactions.
> The transaction doesn't start until all write locks have been
> acquired. If a deadlock occurs trying to get the locks, the locks
> seized are released and the transaction manager starts over.

Ok, then I need one more method in FirebirdConnection (something like
addReservationTable(String) and cleanReservedTables()).

> There is also a mode that seizes and holds table locks as the
> transaction progresses. I haven't a clue what it might be called in
> newspeak. It would probably suffice the stated need. It is prone
> to table deadlocks, however.

Do you know the needed TPB params for this mode?

Thanks!
Roman