forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Dropped Where Statement Bug
- This topic is empty.
-
AuthorPosts
-
-
June 23, 2010 at 8:12 pm #12009IBECJamesMember
So I accidentally came across an interesting bug. If you are updating a row and do not click a separate row to save, but rather change your mode back to Read Only, the History tab shows that the ending WHERE statement is dropped and everything you queried gets the updated information. So instead of just the one row changing, you can have a whole table changed to have every row contain the same information.
-
June 24, 2010 at 4:41 am #30966ShalmaliMember'IBECJames' wrote on '24:
So I accidentally came across an interesting bug. If you are updating a row and do not click a separate row to save, but rather change your mode back to Read Only, the History tab shows that the ending WHERE statement is dropped and everything you queried gets the updated information. So instead of just the one row changing, you can have a whole table changed to have every row contain the same information.
We would like to know the version of SQLyog in which this was encountered. (Because the current version prompts us to save any unsaved data when
we move from Edit to Read only)
~Shalmali
-
July 21, 2010 at 6:58 pm #30967N3WWNMember'Shalmali' wrote on '24:
We would like to know the version of SQLyog in which this was encountered. (Because the current version prompts us to save any unsaved data when
we move from Edit to Read only)
~Shalmali
I just witnessed this same bug which wiped out an entire table, which I could luckily restore from a backup table on another machine.
I am running SQLylog Community – MySQL GUI v8.5 Beta2.
Do you know if this bug was resolved in a newer release?
Thanks!
-Rich
-
July 22, 2010 at 5:54 am #30968ShalmaliMember
Hello,
Apologies for the inconvenience caused. This bug was introduced in 8.4 Release where we started prompting the user to save any unsaved data when we move from
Edit to Read only. We will release a GA with this fix by the end of the day.
Thank you for bringing this to our notice.
~Shalmali
-
July 22, 2010 at 2:37 pm #30969ShalmaliMember
Hello Rich,
We have released 8.55GA and 8.6 Beta 2 simultaneously with this fix.
http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-55-released/
http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-6-beta2-released/
Please upgrade to either of them.
Thank you for your support.
~Shalmali
-
July 23, 2010 at 9:30 pm #30970N3WWNMember'Shalmali' wrote on '22:
Hello Rich,
We have released 8.55GA and 8.6 Beta 2 simultaneously with this fix.
http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-55-released/
http://www.webyog.com/blog/2010/07/22/sqlyog-mysql-gui-8-6-beta2-released/
Please upgrade to either of them.
Thank you for your support.
~Shalmali
Thank you, Shalmali!
I have upgraded to 8.6 Beta 2 and will let you know if I see any other issues.
-Rich
-
-
AuthorPosts
- You must be logged in to reply to this topic.