The last query affected 999 rows

Hi there,

Great software, but here's a killer bug

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

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

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.

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