September 2015 at 14:03, LtColRDSChauhan <rdsc1...@gmail.com> wrote:
>> Message: 3
>> Date: Thu, 17 Sep 2015 19:56:20 +0200
>> From: Ji?? ?in?ura <j...@cincura.net>
>> Subject: Re: [Firebird-net-provider] Multithread insert
>> To: "For user
>
> Message: 3
> Date: Thu, 17 Sep 2015 19:56:20 +0200
> From: Ji?? ?in?ura <j...@cincura.net>
> Subject: Re: [Firebird-net-provider] Multithread insert
> To: "For users and developers of the Firebird .NET providers"
> <firebird-net-prov
015 14:12:25 +0300
> From: zabulu...@gmail.com
> To: firebird-net-provider@lists.sourceforge.net
> Subject: Re: [Firebird-net-provider] Multithread insert
>
> I don't think that the issue in the .NET provider. It just forwards
> options to fbembed.dll for transactions it just
ty sure if you can solve
> this, the firebird team would gladly implement this.
>
> a
>
>
>> Date: Sun, 20 Sep 2015 14:12:25 +0300
>> From: zabulu...@gmail.com
>> To: firebird-net-provider@lists.sourceforge.net
>
>> Subject: Re: [Firebird-net-provider] Multi
Narrowed the problem. The cause is a multithreaded update of the same
record field. Transactions, as I said don't dispatch the issue.
On 17 September 2015 at 17:38, Геннадий Забула wrote:
> lock conflict on no wait transaction
> Acquire lock for relation () failed
> --->
lock conflict on no wait transaction
Acquire lock for relation () failed
---> FirebirdSql.Data.Common.IscException: lock conflict on no wait
transaction
Acquire lock for relation () failed
On 17 September 2015 at 17:38, Геннадий Забула wrote:
> I was wrong about
On Thu, Sep 17, 2015, at 17:57, Геннадий Забула wrote:
> Narrowed the problem. The cause is a multithreaded update of the same
> record field. Transactions, as I said don't dispatch the issue.
The advice is simple. Don't update same record (not only in .NET;
anywhere, anytool). :D
--
Mgr. Jiří