On 11/5/20 2:24 PM, Dimitry Sibiryakov wrote:
05.11.2020 12:10, Alex Peshkoff via Firebird-devel wrote:
They want to modify same record. When that happens in 2 different
transactions, started from 2 different attachments (specially pay
attention that one is started and committed in DFW of another one) -
you see, deadlock is unavoidable.
Why deadlock if it is an ordinary update conflict? Starting NOWAIT
transaction in plugin would be a natural solution, no?
That will resolve a conflict but will not make user's code work as
expected and as it does with separate sec.db.
The only issue is that it's high time to rewrite everything related
to metadata in this plugin to make it use FB_MESSAGE instead local
templates - it was written before FB_MESSAGE arrived.
I see FB_MESSAGE already used in SrpServer, reusing it in
SrpManagement shouldn't be so hard but still ugly.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
