G
George Potemkin
Guest
> your example has an explicit transaction block, so maybe dbtaskid() should start one in that case. Inside the transaction block (explicit or not) DBTASKID() returns a transaction number after any db request (for example, after reading a sequence, VST or application's table). At the same moment the session creates the entry in transaction table in shared memory. Yes, transaction may become ACTIVE some time later when the changes are saved to the database. But the value of DBTASKID() function is not related to the transaction status.
Continue reading...
Continue reading...