12.09.2018 2:45, 'Hamish Moffatt' ham...@risingsoftware.com [firebird-support]
wrote:
> Unfortunately your journal / batch update solution doesn't help in my case.
What's wrong with it in your case?
--
WBR, SD.
]
Enviado: quarta-feira, 12 de setembro de 2018 00:50
Para: firebird-support@yahoogroups.com
Assunto: Re: [firebird-support] how to resolve this deadlock
On 10/09/18 22:52, Hugo Eyng hugoe...@msn.com<mailto:hugoe...@msn.com>
[firebird-support] wrote:
Hi Hamish.
I am not sure if I unde
On 10/09/18 22:52, Hugo Eyng hugoe...@msn.com [firebird-support] wrote:
>
> Hi Hamish.
>
> I am not sure if I understood clearly your problem. If I did, you
> probably should use "WITH LOCK" clause.
Thanks Hugo, that might work. But as the row might not exist yet, I
would have to lock the whole
On 11/09/18 00:48, Svein Erling Tysvær setys...@gmail.com
[firebird-support] wrote:
> Hi Hamish!
>
> What exactly do you mean by "The queries kind of don't
> actually conflict"? If they're trying to MERGE into the same row
> simultaneously, then they do actually conflict, even if they contain
Hi Hamish!
What exactly do you mean by "The queries kind of don't actually conflict"?
If they're trying to MERGE into the same row simultaneously, then they do
actually conflict, even if they contain the same values. Strictly speaking,
I think you have a 'lock conflict' and not a 'deadlock' (a
Hi Hamish.
I am not sure if I understood clearly your problem. If I did, you probably
should use "WITH LOCK" clause.
Atenciosamente,
+ + Hugo Eyng + +
De: firebird-support@yahoogroups.com em nome
de 'Hamish Moffatt' ham...@risingsoftware.com
