I am having some strange behavior after deletes. My theory is that it arises when I delete records made by perl scripts with the command line tool (./mysql). While my theory is based on solid observation, I dont really believe it. Here is what happens:

In the course of testing cgi scripts I run the script a few times and then go into the database via command line and delete the saved rows. After the delete the script often fails telling me that it can not insert the new row because a duplicate row already exists. This is strange so i flush tables. The error is not refering to a unique key, the key it complains about is quite clearly MUL when describe is called.

My current tact is to use the command line tool less and dare the error to return, but that has inconveniences.

any suggestions or pointers will be appreciated -adam

------------------------------- related information: mySQL version: 3.23.53 Mac OSX server 10.2

mysql> describe images; +-------------+----------------------+------+-----+--------- +----------------+ | Field | Type | Null | Key | Default | Extra | +-------------+----------------------+------+-----+--------- +----------------+ | Image_ID | smallint(5) unsigned | | PRI | NULL | auto_increment | | Account_ID | smallint(5) unsigned | | MUL | 0 | | | Name | varchar(24) | YES | | NULL | | | Description | varchar(36) | YES | | NULL | | | Category | tinyint(3) unsigned | YES | | 1 | | | SRC | tinytext | YES | | NULL | | +-------------+----------------------+------+-----+--------- +----------------+ 6 rows in set (0.01 sec) it complains about the Account_ID field after I delete where account_id =