[peterlaursen]

Form our (Webyog) side we will not provide that option directly in SQLyog. SQLyog is a client for the MySQL server. It is not a tool for application programming, and there is no reason why PHP should be considered more important than .NET or JAVA or whatever client environment.

[peterlaursen]

Can you provide a complete test case? A dump of the table and the query? You may send to [email protected] if you don't want to share in public. And it need not be your original data – it can be any set of 'dummy data' as long as it is reproducible.

[peterlaursen]

Update: The idea of of a tunneler for 'generic use' was abandoned shortly after I wrote my last reply. There are no such plans.

[peterlaursen]

We abandoned this idea shortly after I replied in the other post. There will not be a version of the tunneler for 'generic use'.

I will update the other posts accordingly.

[peterlaursen]

Well .. we can add this a a 'feature request' here https://code.google.com/p/sqlyog/issues/list, if you insist, of course. But there is no chance that it will be considered in foreseeable future. We implemented the Object Browser filter for same reason. And I believe it should be possible to name tables so that the filter can be used.

However we do plan (soon – in a few months probably) however to add support for regular expressions in the OB filter and once implemented it should be even eaiser to name tables and other objects is such a way that a filter can be specified.

[peterlaursen]

Sorry .. my link was wrong. It should have been:

https://code.google.com/p/sqlyog/issues/detail?id=190

[peterlaursen]

Well .. you are referring to this discussion http://forums.webyog.com/index.php?showtopic=7359 I think?

[peterlaursen]

i have added this to our issue tracker http://forums.webyog.com/index.php?showtopic=7352.

Ther are more problems with the context dialo is connection uses a non-strict SQL_mode. Those will be even more confusing with keyboard shortcuts, I believe.

We will discuss this and update here (but it may take a few weeks).

[peterlaursen]

And what then if the column is defined NOT NULL?

In that case *SET TO NULL' is 'greyed out' in the context menu of the cell. So user will see that this is not an option. But with a keyboard shortcut the context menu will not display and it will be confuing that the shortcut has no effect, I think?

Also why not also a shortcut for 'SET TO DEFAULT' and 'SET TO EMPTY STRING' then? We also have very few free shortcut key combinations left that are not in use!

I do understand that a simple shortcut is nice as a replacement for typing, but there should be consistency and no confusion in the interface.

[peterlaursen]

It is not quite non-trival. The Data/result GRID in SQLyog is our own code (a 'class' in C++-terminology I belive) and it has currently no option for tooltips.

[peterlaursen]

This error is delat with in our FAQ here: http://faq.webyog.com/content/23/15/en/error-no-2003-can_t-connect.html

Does this error occur when connecting to the same server as where it used to work?

Anyway this error is not specific for SQlyog. Any client installed on same machine as SQLyog connecting to same server will return the same error. It is the MySQL client API that returns the error. Please refer: MySQL documentation: http://dev.mysql.com/doc/refman/5.5/en/error-messages-client.html

(and please *attach* images using the GUI option for same rather than posting the binary string)

[peterlaursen]

Ctrl+SPACE as it is already used by Autocomplete. Actually we have very few keyboard sshortcut combinations that are not in use already.

What SQLyog 'flavor' are you using? Community or one of the commercial versions? Autocomplete is included in all commercial 'flavors'. In all those you may type a database name followed by a “'.” (dot/punctuation9 and the columns list will popup. Please refer documentation at https://static.webyog.com/docs/SQLyog/AutoComplete_for_SQLyog_MySQL_Manager.htm

[peterlaursen]

You alos sent a mail with same content. Please decide to communitate over our support mail or here. If discussion si spread over multiple places it is easy to miss some details.

I will paste my reply to your mail here:

Quote:

I really doubt that this is because of the upgrade. The HTTP-tunneling code has not been modified even the slightest for 3 or probably 4 years. I believe it would also had happened it you had not upgraded. The reason is another, I believe, and it is coincidence that it happens almost the same time as you upgrade.

But anyway .. is there any pattern when this happens? Or does it just seem to happen randomly? Does it happen only in copy table/database? If so .. does it happen with specfic tables only? How big are the tables affected in that case?

It looks like a networking problem or some configuration change on the remote site. You may install the old version in parallel (to another folder) to verify/check that. Or it could be because tables have grown to big for the PHP configuration (ther is a MAX_PACKET setting or something like that as far as I remember).

Also do you remember what version you had before?

[peterlaursen]

Maybe this blog will also help?

http://blog.webyog.com/2009/11/06/amazon-rds-the-beginners-guide/

(but it is 4 years old, so Amaxon's interface may have changed since then)

[peterlaursen]

Are you sure that there is not a conclict with another program on port 80?

[Author]

Posts