The last query affected 999 rows
| User, date | Message |
|---|---|
|
Written by muzza4
6 years ago Category: General 50 posts since Mon, 04 Dec 06 |
Hi there, Great software, but here's a killer bug… 1. run a query like 'select field1 from table' WARNING: don't do this on a production table anyone 2. in the query results change a value and leave the field 3. program replies "Warning: consistency problem detected. The last query affected 999 rows, when it should have touched only 1 row! This is most likely caused by not having a primary key in the table's definition." Regardless of the definition of the table (it does have a primary key in my case anyway) you can't destroy a database like this! If you can't avoid the problem the program shouldn't let query result values be modified. If you can avoid the problem...urgently would be good. Thanks |
|
Written by siMKin
6 years ago 104 posts since Sun, 01 Apr 07 |
If you select only 1 column, there is no PK in the data-set, so it's actually not so strange this happens. Since you have no way of knowing which particular record you are editing, how should Heidi know? If you select more columns (preferably a PK field) this doesn't happen maybe also take a look at this topic: http://www.heidisql.com/forum/viewtopic.php?t=47 |
|
Written by muzza4
6 years ago 50 posts since Mon, 04 Dec 06 |
Thanks for that. I now understand. However I can't agree with this "it's your problem" approach - if this product is for everyone then it needs to get this bit right. I have tested this issue in MySQL-Front. The user is not able to update a field unless a primary key is specified. I would recommend this approach be taken here. Thanks |
|
Written by siMKin
6 years ago 104 posts since Sun, 01 Apr 07 |
wrote: However I can't agree with this "it's your problem" approach - if this product is for everyone then it needs to get this bit right. I didn't mean to support any "it's your problem" approach .. i was merely explaining what happened :) As i've written in the other topic: i think it's good if Heidi disables it by default, thereby protecting its users, but with the possibility to override it at your own risk. |
|
Written by muzza4
6 years ago 50 posts since Mon, 04 Dec 06 |
Hi siMKin, I saw in the other topic that we are on the same page here. I intended the "it's your problem" phrase to apply to the software's functionality, not to anyone personally. Cheers |
|
Please login to leave a reply, or register at first. |