Den 02.12.2015 13:24, skrev Ann Harrison aharri...@ibphoenix.com
[firebird-support]:
>> On Dec 2, 2015, at 6:35 AM, Tim Ward t...@telensa.com [firebird-support]
>> wrote:
>>
>> What about if two concurrent transactions are both trying to *delete*
>> the *same*
On Wed, Dec 2, 2015 at 11:49 AM, Tim Ward t...@telensa.com
[firebird-support] wrote:
>
>
> Yes I do know it's not a real deadlock, I was using the word because I
> knew it would be understood and because, I'm pretty sure?, I've seen it
> in one of the relevant
Thanks for the replies.
Don't worry folks, I'm not going to try this, I was just curious.
Yes I do know it's not a real deadlock, I was using the word because I
knew it would be understood and because, I'm pretty sure?, I've seen it
in one of the relevant error messages.
--
Tim Ward
I know that if two concurrent transactions try to make changes to the
same record at the same time one of them gets a deadlock.
What about if two concurrent transactions are both trying to *delete*
the *same* record at once? - from the point of the view of the user's
objectives there's no
> On Dec 2, 2015, at 6:35 AM, Tim Ward t...@telensa.com [firebird-support]
> wrote:
>
> What about if two concurrent transactions are both trying to *delete*
> the *same* record at once? - from the point of the view of the user's
> objectives there's no