On Fri, Jun 06, 2003 at 09:03:04PM -0400, Becoming Digital wrote:
> just suppress the error with @.
>
Oh yes, I forgot about that one.
But the other discussion was more fun!
Regards,
Mark
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsub
I need a placeholder statement that does nothing.
Is there something more elegant than
SELECT FROM ... WHERE 0=1; ?
I need this because PHP throws an error when an empty statement
(or just a ';') is passed to MySQL.
Regards,
Mark
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archiv
I do it?
Regards,
Mark
[EMAIL PROTECTED]
>
>
> ----- Original Message -
> From: "Mark Rages" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: June 5, 2003 7:52 PM
> Subject: I thought single UPDATE statements were atomic
>
>
> > Ac
On Fri, Jun 06, 2003 at 01:07:43PM +0200, Jon Haugsand wrote:
> * Mark Rages
> > According to the docs, single update statements are atomic.
>
> I would not say that your problem is with atomicity, but with
> consistency. It is expected that a transaction oriented database
&
According to the docs, single update statements are atomic.
So why doesn't this work?
mysql> create table t (num INT, UNIQUE (num));
Query OK, 0 rows affected (0.00 sec)
mysql> insert into t values ('1');
Query OK, 1 row affected (0.00 sec)
mysql> insert into t values ('2');
Query OK, 1 row aff
On Thu, Jun 05, 2003 at 09:09:36PM -0500, Paul DuBois wrote:
> At 18:52 -0500 6/5/03, Mark Rages wrote:
> >According to the docs, single update statements are atomic.
>
> That's correct.
>
> Consider what happens if MySQL tries to update the first record and
>
