Mike,
- Original Message -
From: "Mike Gohlke" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Saturday, December 07, 2002 6:44 PM
Subject: Re: Innodb row locking question
>
>
> Benjamin Pflugmann wrote:
>
> >Hello.
> >
> &
Hello.
On Sat 2002-12-07 at 10:36:00 -0600, [EMAIL PROTECTED] wrote:
[...]
> >Why do you repeat "job_id = 111 and thread_id = 0"? If you are using a
> >transaction seperation level of at least REPEATABLE READ (which is the
> >default), InnoDb assures that you always see the same rows within one
>
Benjamin Pflugmann wrote:
Hello.
On Fri 2002-12-06 at 10:28:23 -0600, [EMAIL PROTECTED] wrote:
Heikki and all,
I've got a quick question which may be more general sql related but
since I'm using innodb tables specifically for the row locking.
The following process description is specifical
Hello.
On Fri 2002-12-06 at 10:28:23 -0600, [EMAIL PROTECTED] wrote:
> Heikki and all,
> I've got a quick question which may be more general sql related but
> since I'm using innodb tables specifically for the row locking.
>
> The following process description is specifically designed to prevent
Heikki and all,
I've got a quick question which may be more general sql related but
since I'm using innodb tables specifically for the row locking.
The following process description is specifically designed to prevent
duplicates.
My current process:
select * from run where job_id = 111 and thread
