Hello,

I use Firebird BLOBs to store documents. My transactions could be
safely split in two parts, one that stores the document, one that
shows it to the 'world'. The purpose to have the long part in the
first transaction which does not prevent any concurrent work and the
second transaction which must lock some stuff would be very fast.

I would like something like this:
-----
start first transaction
create the blob and store it in table A row 1
commit the transaction

start second transaction
lock some useful things
open row 1 in table A, get the blob id, then remove the row
create a new row 2 in table B and store the blob id
commit second transaction
-----

is it possible?

Regards,
Armel