I don't think that the issue in the .NET provider. It just forwards
options to fbembed.dll for transactions it just TPB. And do it right.
The problem is in the engine, I've retested it with C API and the
behavior is similar to observed. My case is similar to the described
here:
>
> Message: 3
> Date: Thu, 17 Sep 2015 19:56:20 +0200
> From: Ji?? ?in?ura
> Subject: Re: [Firebird-net-provider] Multithread insert
> To: "For users and developers of the Firebird .NET providers"
>
> Message-ID:
>
I don't think there is even an issue here. inside two different transactions,
you simply cannot update the same record. Who would win in the end and what
would be the end result. I'm pretty sure if you can solve this, the firebird
team would gladly implement this.
a
> Date: Sun, 20 Sep 2015
> I don't think there is even an issue here
After taking another view at what happens, I don't think either.
The exception is thrown when similar updates are made for one field,
from several threads, when NO_WAIT specified. Only this flag causes it
to throw. No matter if you specify flags