Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

The last query affected 999 rows

muzza4's profile image muzza4 posted 14 years ago in General Permalink
Hi there,

Great software, but here's a killer bug
siMKin's profile image siMKin posted 14 years ago Permalink
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
muzza4's profile image muzza4 posted 14 years ago Permalink
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
siMKin's profile image siMKin posted 14 years ago Permalink

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.
muzza4's profile image muzza4 posted 14 years ago Permalink
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
Code modification/commit 6e9778c from ansgarbecker, 4 years ago, revision 5149
Revert r5144, which causes more problems than it solves. See
* http://www.heidisql.com/forum.php?t=23009
* http://www.heidisql.com/forum.php?t=23243
* http://www.heidisql.com/forum.php?t=23196
Code modification/commit 64c43ae from Ansgar Becker <anse@heidisql.com>, 2 years ago, revision 5707
Issue #62: distinct between TIMEZONE (without time zone) and TIMEZONETZ (with time zone). And modify GetDatatypeByName() so it deletes the longest detected datatype string PostgreSQLDatatypes.Names . This solves empty/undetected column comments in ParseTableStructure(). See https://www.heidisql.com/forum.php?t=23211#p34709

Please login to leave a reply, or register at first.




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.