Hello.
> | 4.0.17-standard |
It is an old version of MySQL which could contain lots of bugs. It is
strongly recommended to upgrade to the latest release 4.1.12, or if it
is impossible in your production environment to 4.0.24. Usually upgrade
solves such kind of errors. Please, next
ag
>
>
> -Original Message-
> From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 30, 2005 3:20 PM
> To: mysql@lists.mysql.com
> Subject: Re: Duplicate entry error
>
>
> Hello.
>
> Please examine your master's
in for your help and cooperation.
Anurag
-Original Message-
From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 3:20 PM
To: mysql@lists.mysql.com
Subject: Re: Duplicate entry error
Hello.
Please examine your master's binary and slave's relay logs with
Hello.
Please examine your master's binary and slave's relay logs with
mysqlbinlog utility to find if sent and received SQL statements are
different. Sent your MySQL versions on master and slave. Include complete
output of 'SHOW SLAVE STATUS'. If your version is rather old, check if the
prob
You have set EKey to be unique, so if you already have another row with
EKey = 13, you cannot establish an additional row with the same key.
(unique keys can be either set by primary key(), or unique())
.. Atle
On Mon, 12 Feb 2001, Paul Wilkinson wrote:
> Thanks in advance for your help!
>
Hi,
You have a unique key defined which includes Ekey and another field (the key
2 mentioned in the error message), and the entry "other_field = '88' and
Ekey='252'" has already been used.
Regards
Quentin
-Original Message-
From: Paul Wilkinson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday,
