Mark,
<snip>
> I'm using InnoDB tables, which are reputed to be ACID compliant.
> Same problem.
>
> I guess I will follow your suggestion and just drop the UNIQUE
> constraint since it appears to be evaluated after each row is
> UPDATEd and not after the UPDATE completes.
>
> I'll check out how Postgres and Firebird handle this.
> (Anyone want to try it on Oracle for me?)
>
> Regards,
> Mark
> [EMAIL PROTECTED]
>
This is Oracle's take on your issue:
SQL> create table test (col1 number(1) primary key);
Table created.
SQL> insert into test values (1);
1 row created.
SQL> insert into test values (2);
1 row created.
SQL> commit;
Commit complete.
SQL> update test set col1 = col1 + 1;
2 rows updated.
SQL> commit;
Commit complete.
SQL> select * from test;
COL1
----------
2
3
2 rows selected.
SQL>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
