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

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: New Ui Makes Me Frustrated #33047
    Kevin Sikes
    Member

    I also would find it helpful to move the info tab back to the lower half of the main screen, for the same reasons mentioned by SimonGalaxy.

    Thanks,

    Kevin Sikes

    in reply to: Autocomplete Broken In 9.32 For Aliased Tables #32833
    Kevin Sikes
    Member

    Yes, autocomplete would need to be aware of the relationships between tables to suggest JOIN predicates. I hope you will consider adding this ability; other tools provide it (including a popular free tool for MySQL), but I would rather use SQLyog and not switch between tools. Thanks!

    in reply to: Autocomplete Broken In 9.32 For Aliased Tables #32831
    Kevin Sikes
    Member

    Hi Peter,

    I appreciate that your team has found and fixed this issue so quickly, and I also appreciate your willingness to provide a one-off build. However, it's not necessary — I have reverted to 9.30 for the time being. Take your time with the new release.

    By the way, will autocomplete ever suggest JOIN predicates? For instance, in the sample code I provided, after typing ON will SQLyog ever suggest b.`SaleID` = s.`SaleID` ? That would be very useful. Thanks!

    Kevin Sikes
    Member

    It appears you have misunderstood my concern. The term “portable” has a very specific meaning in current parlance: configuration and data are kept on removable media and no changes are made to the host computer.

    Let's say “Bill” is doing work at a customer's site. Bill is a licensed SQLyog user. The site does not allow Bill to connect his laptop to the network, so he uses one of their machines and runs SQLyog from a thumb drive, since you represent your software as being portable. He is prompted for his license info, which unbeknownst to Bill is stored on the customer's computer. According to your statement, “Basically he must ensure (with a single user license) that he is the only user of the program and that the program is only used on one computer at a time”, how will Bill ensure anything of the sort, since his “portable” installation stored a license key on his customer's computer?

    Kevin Sikes
    Member

    So in essence, only the Community version is truly portable?

    Kevin Sikes
    Member

    I have created a portable install of SQLyog Ultimate ver. 9.10 on a USB thumb drive. The -dir parameter works correctly; however, I am prompted to enter my license info every time I plug the thumb drive into a different computer. This leads me to believe that the host computer is being modified unexpectedly (and it doesn't seem truly portable.) Shouldn't the license info be saved as some sort of hash on the thumb drive itself?

    Thanks,

    Kevin Sikes

    in reply to: #28142
    Kevin Sikes
    Member
    'peterlaursen' wrote on '11:

    We have more requests for seach/find (multiline search/replace, wildcards, regular expressions). We will reply back shortly to all.

    No “find next” is still a huge bummer for me. Any news? It's been 16 months, and you said you'd get back to me shortly.

    Thanks,

    Kevin

    in reply to: #28140
    Kevin Sikes
    Member

    The minimum word length for full text searches is configurable by setting the ft_min_word_len variable and rebuilding your full text indexes. Obviously, this won't work for hosted sites — perhaps that is what you meant when you said “it is not our application.”

    More importantly, do you have any comment on the Ctrl+F vs. F3 behavior in the Query Editor?

    Thanks,

    Kevin Sikes

    in reply to: #27647
    Kevin Sikes
    Member

    A situation like this is where best practices can guard against trouble. For instance, consider this command:

    DELETE FROM SomeCriticalTable WHERE UserID=12345

    If you start typing in natural order and get to this point when the query is unexpectedly submitted, you're in trouble! :

    DELETE FROM SomeCriticalTable

    It's better to put a stub in for the DELETE command and fill it in after your WHERE clause is complete:

    DL FROM SomeCriticalTable WHERE UserID=12345

    Once the WHERE clause is complete, go back to the beginning of the line and replace DL with DELETE. Now you'll get a harmless syntax error if your query is inadvertently submitted while you are constructing the rest of your query.

    Kevin Sikes

Viewing 9 posts - 1 through 9 (of 9 total)