Hi,
this is my system:
mysql> status
--
mysql Ver 14.12 Distrib 5.0.26, for suse-linux (x86_64) using readline 5.1
Connection id: 142883
Current database: mysql
Current user: root@localhost
SSL:Not in use
Current pager: less
Usin
Bernd wrote:
> a password ?
>
> Hi,
>
> this is my system:
>
> mysql> status
> --
> mysql Ver 14.12 Distrib 5.0.26, for suse-linux (x86_64) using readline 5.1
>
> Connection id: 142883
> Current database: mysql
> Current user: root@localhost
> SSL:
> If the return value of the UPDATE stmt is zero, the following stmt is ran:
By return value I assume you mean "rows affected" ?
> This is working great, and has been for many years; however,
> today I noticed it was not working on a particular MySQL server.
By "not working" what exactly is the
Found the problem here, someone had created on insert and on update
triggers on this table that were interferring with the process.
This logic works wonderfully when you need sequence numbers that are also
transaction safe. The key is you need a unique index on all the columns
involved.
I think m
