Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Dropped Where Statement Bug

forums forums SQLyog SQLyog: Bugs / Feature Requests Dropped Where Statement Bug

  • This topic is empty.
Viewing 5 reply threads
  • Author
    Posts
    • #12009
      IBECJames
      Member

      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.

    • #30966
      Shalmali
      Member
      '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

    • #30967
      N3WWN
      Member
      '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

    • #30968
      Shalmali
      Member

      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

    • #30969
      Shalmali
      Member

      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

    • #30970
      N3WWN
      Member
      '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

Viewing 5 reply threads
  • You must be logged in to reply to this topic.