[Marty Martin]

'peterlaursen' wrote on '27:

Well .. then it is all explained.  The WHERE clause in the DELETE statement will match all rows. I am not able to understand why you want to have duplicate rows.  But you may copy the DELETE statement from HISTORY tab and add “LIMIT 1” at the end.  But there still is no way to control *which* of the rows is deleted.  The MySQL server will delete the first one it finds.  Even the server cannot distinguish them. You should have a Primary Key in you tables.

Agreed. I don't want duplicate rows; the problem was in importing data from spreadsheets, there would often be duplicate rows of data, but when I would try to delete all but one of the duplicates, it deleted them all. I added the PK and all is fine now. Thanks!

[Marty Martin]

'peterlaursen' wrote on '23:

But what is your setting here?

[attachment=1325:multi.jpg]

I have that unchecked because it's a real pain when I delete 50 rows to have it prompt me “Are you sure” every 5/random number of rows.

[Marty Martin]

Okay, thanks to both of you, this definitely answers my question. Time to insert a primary key column 🙂

[Author]

Posts