Found the source of my problem.
I had an update trigger connected to this table which was trying to
create a new entry in another table instead of updating an existing one!
There we go!
Simon
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http:
Hi Michael
Here is the table schema :
DROP TABLE IF EXISTS `clients`.`calendarentry`;
CREATE TABLE `clients`.`calendarentry` (
`idCalendarEntry` int(10) unsigned NOT NULL auto_increment,
`Sujet` varchar(80) NOT NULL,
`Debut` datetime NOT NULL,
`Fin` datetime NOT NULL,
`Notes` varchar(2048)
Simon,
send in the schema for the table in question, that should show
something. The only condition I can think of off the top of my head
which might do that is if you have another unique key in your
structure and that is the one this error is complaining about.
On 2/12/07, Simon Giddings <[
Hi MySQLeers,
How can I setup multiple daemons, One daemon for one database? So that they
can act independenly. What might be the pitfalls over here?
In what situation one can opt for multiple daemons?
What about maximum_connections. Is it for all the server instances?
Thanks
DEVI. G
- Original Message -
From: "Devi" <[EMAIL PROTECTED]>
To:
Sent: Monday, February 12, 2007 5:34 PM
Subject: Re: Update failing with error 1062
Hi MySQLeers,
How can I setup multiple daemons, One daemon for one database? So that
they can act independenly. W
Good morning,
I issue an update statement containing a where clause on the primary
index, so as to update a single record. Howerver this is failing with
"Duplicate entry '6' for key 1" -
update clients.calendarentry set Subject = 'presentation' where
idCalendarEntry = 6;
In the table, the fi
