Subject | Re: [Firebird-Architect] Vulcan architecture and lock tables |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2006-12-18T10:30:22Z |
= m. Th = wrote:
In any case, an admin don't need to know the transaction that is trying
to update a record, but the one that prevents others to update it.
Adriano
>> The one that holds the lock. Our transaction number is alreadySorry, but I disagree.
>> accessible, no need to report it.
>>
>>
> How? Remember, I speak from the *application developer* POV. In a
> complex code IMHO is very hard to find which TID is the offending one,
> even the communication layer with Fb 'knows' it. And, also, perhaps,
> some libraries don't even expose it.
In any case, an admin don't need to know the transaction that is trying
to update a record, but the one that prevents others to update it.
Adriano