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

Major Bug — Wrong Queries Executed!

forums forums SQLyog SQLyog: Bugs / Feature Requests Major Bug — Wrong Queries Executed!

  • This topic is empty.
Viewing 10 reply threads
  • Author
    Posts
    • #9352
      ronald
      Member

      After playing with 5.0, I was shocked to see that for some reason SqlYog was executing the wrong statements when I was pressing F5. In my case, it was unfortunately a delete statement for some data that I needed (luckily the data wasnt that crucial).

      I was determined to find what was going on, and after much experimentation I have found that number of previous semicolons in the query editor offset the character position SqlYog thinks is the active statement by -1. Consider the following example:

      select 'w';

      select 'x';

      select 'y';

      select 'z';

      Placing the cursor at any point on the first statement and pressing F5 returns 'w' as expected.

      Placing the cursor after the apostrophe and before the semicolon of the second statement and pressing F5 returns 'y', when the result should be 'x'!!! putting the cursor at any other position on the second statement correctly returns 'x'

      On the third statement, placing the cursor anywhere after the y and pressing F5 will wrongly return 'z'…. and so on and so forth. Now consider this illustration:

      ;;;;;;;;;;;

      select 'w';

      select 'x';

      placing the cursor ANYWHERE on the first statement and pressing F5 will wrongly return 'x', when the correct result would be 'w'

    • #19730
      Ritesh
      Member

      Bug confirmed. Will be fixed in v5.01.

    • #19731
      ronald
      Member
      Ritesh wrote on Nov 10 2005, 11:33 AM:
      Bug confirmed. Will be fixed in v5.01.

      [post=”7874″]<{POST_SNAPBACK}>[/post]

      Sweet — I'm still forced to use 4.0 BETA 5, which doesn't have this bug, nor this bug: http://www.webyog.com/forums/index.php?showtopic=1532

      If you could hook a brother up with a fix for both of these in 5.01 I'd gladly finally register!

    • #19732
      Ritesh
      Member

      Thank you for the bug report.

      I would be happy to provide you with a free license of SQLyog Enterprise. Just send a mail to [email protected] regarding the same.

    • #19733
      vygi
      Member
      Ritesh wrote on Nov 11 2005, 12:12 PM:
      Thank you for the bug report.

      I would be happy to provide you with a free license of SQLyog Enterprise. Just send a mail to [email protected] regarding the same.

      [post=”7879″]<{POST_SNAPBACK}>[/post]

      hey – cool! 😉

      somebody has got a fee license just for re-submitting an OLD bug!

      I have submitted the same problem already three times here, provided detailed descriptions and examples, look here: http://www.webyog.com/forums/index.php?showtopic=1739

      1: Oct 13 2005, 03:59 PM (4.2 beta 5)

      2: Oct 26 2005, 01:33 PM (4.2 RC1)

      3: Nov 2 2005, 11:37 AM (4.2 RC2)

      All what I got was a personal message saying that it will be fixed in 5.1.

      (this was also the only reason why I've not re-submitted it again for the final 5.0)

      A bit unfair — isn't?… 🙁 — where are my licenses?..

    • #19734
      Ritesh
      Member

      I will be happy to provide you with a free license. Just send a mail to our sales people at [email protected].

    • #19735
      vygi
      Member

      wow – thanks a lot!

      In return, I will do my very best in testing and reporting further possible problems (but hope that there will be not much of them).

      All the best,

      Vygi

      P.S. …and next time better don't post your gifts that openly as everybody (like me) becomes envious of it…

    • #19736
      Ritesh
      Member

      I had messaged you with info on 5.01 BETA. Did the BETA fix the problem?

    • #19737
      earlati
      Member
      Ritesh wrote on Nov 25 2005, 08:49 AM:
      I had messaged you with info on 5.01 BETA. Did the BETA fix the problem?

      [post=”7991″]<{POST_SNAPBACK}>[/post]

      Please can you made the beta revision available worldwide.

      In any case is not possible to use the offcial 5.0 revison( also I have to reinstall the older revision) so if the beta is available,many people can start to use and test it.

      regards, Enzo

      PS. mybe what follow should help.

      Inside a query windows I have the statements showed belowe.

      Till the line 13 , when I press F5 I run the right query , while when I press F5 on the 14th line I run the 15th line

      Also inside the 13th line the thinks works differnetly

      If I press F5 while the cursor in on the point under the char 3 I run the 13th statement ( the right one ) while if I move the cursor on positon befor the last ' I run the 14th statement ( the wrong one )

      In this example the blank inside the string are tabs, but I found also with simple string of blank chrs and the result is the same ( just the line when the problem begin is the 17th instead of 14.

      Select ' 1 ' FROM DUAL;

      Select ' 2 ' FROM DUAL;

      Select ' 3 ' FROM DUAL;

      Select ' 4 ' FROM DUAL;

      Select ' 5 ' FROM DUAL;

      Select ' 6 ' FROM DUAL;

      Select ' 7 ' FROM DUAL;

      Select ' 8 ' FROM DUAL;

      Select ' 9 ' FROM DUAL;

      Select ' 10 ' FROM DUAL;

      Select ' 11 ' FROM DUAL;

      Select ' 12 ' FROM DUAL;

      Select ' 13 ' FROM DUAL;

      Select ' 14 ' FROM DUAL;

      Select ' 15 ' FROM DUAL;

      Select ' 16 ' FROM DUAL;

    • #19738
      vygi
      Member
      Ritesh wrote on Nov 25 2005, 07:49 AM:
      I had messaged you with info on 5.01 BETA. Did the BETA fix the problem?

      [post=”7991″]<{POST_SNAPBACK}>[/post]

      Sorry for delay….

      Yes, this new versions works correctly, no problems detected so far!

      Vygi

    • #19739
      Ritesh
      Member

      SQLyog v5.01 BETA has been released. More details at: http://www.webyog.com/forums/index.php?act…&st=0#entry8102

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