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
...@risingsoftware.com [firebird-support] <
> firebird-support@yahoogroups.com>
> *Enviado:* segunda-feira, 10 de setembro de 2018 08:46
> *Para:* firebird-support@yahoogroups.com
> *Assunto:* [firebird-support] how to resolve this deadlock
>
>
>
> I have a bunch of us
[firebird-support]
Enviado: segunda-feira, 10 de setembro de 2018 08:46
Para: firebird-support@yahoogroups.com
Assunto: [firebird-support] how to resolve this deadlock
I have a bunch of users logging in to my system at the same time, which
causes a simple query like this to run:
UPDATE OR INSERT IN
I have a bunch of users logging in to my system at the same time, which
causes a simple query like this to run:
UPDATE OR INSERT INTO G_CLASS (CLASS_NUM, CLASS_NAME, USER_NUM,
SYLLABUS_NUM)
VALUES (1, 'Foo', 1001, 43)
The field values are identical for each - it's exactly the same query.
