Empty Table Data Tab On All Tables! Help!

[Patrick M]

Hello all!

Great product, I have been using it since early version 3 and have loved it the whole time. Never had any real issues with it until just recently. I'm a SQLYog evangelist for sure, and have brought it to at least two workplaces where it is now used by a number of people. I like MySQL, and I love SQLYog!

I have not changed any connection settings on connections I have been using for months, and the permissions of the users I'm using to connect to the servers have not changed either. For some reason, however, last week sometime SQLYog just started refusing to populate the “Table Data” tab. I upgraded to version 6.03 hoping it was an issue in my previous version but that doesn't seem to have fixed it. In fact, it seems to have made it worse! Now it only ocassionally reports data in tables even when I manually write and execute SQL statements like SELECT * FROM table. I don't think it's a permission issue because it's happening on all of the two or three connections I use most, which are different machines with different users. I think I must have hit a switch somewhere and broken something inside of SQLYog sometime recently.

Yes, the tables have data in them, as reported by the mysql command line utility and our local install of phpMyAdmin.

Any ideas what could be causing this absolutely bizarre behavior?

Any and all input would be appreciated! I don't want to have to go back to dealing with phpMyAdmin! ERGH!

Thanks,

-Patrick

[peterlaursen]

“last week sometime SQLYog just started refusing to populate”

and

“Now it only ocassionally reports data in tables”

and

“it's happening on all of the two or three connections I use most”

To me all this indicates an issue on the network.  Some kind of termination of the stream of data. A program like SQLyog will not “sometimes” do like this.  But I cannot explain why SQLyog does this and other clients not.

It is not a permission issue.  The server would then send an error message and SQLyog would print that error.

Can you experiment with different types of connection?  Different localities for the client machine?  Could we have remote access to one of those servers?

[peterlaursen]

Some additional remarks and considerations:

The random nature of this problem ('it happens most of the time with most connections') indicates to me that it is not a SQLyog issue.  Such issue would not be random like this, it would either work or it would not!

If phpMyAdmin works on that host, then please try SQLyog with HTTP tunnelling.  This should be the same a phpMyAdmin in this respect: connection to MySQL from 'localhost' and transfer of data to SQLyog using HTTP.

Also please note that when no data occurs in SQLyog after a ” SELECT * …” does the 'execute' icon in the program display a 'green arrow' or a 'red cross' ?  If the latter is the case, this means that SQLyog is still waiting for data to be transferred.

[Patrick M]

Peter,

Thanks for your reply.

I feel really silly. It was nothing even as remotely complicated as permissions or network issues. I can't believe I struggled for weeks with it, then became convinced an app as consistently stable as SQLYog could be doing something this strange. You're going to think I'm an idiot, and I'd like to think I'm not, but it might help someone out sometime so I'll put it here

In the Table Data tab, you can limit the number of lines your “preview” query will return. This can be a nice feature for tables with lots of records, and a [seemingly] harmless one on tables with fewer records than the limit. If you have the bright idea sometime to limit the number of records returned to 0, hoping that maybe that will mean “return ALL the results” and not seeing the “Show All” checkbox right next to it, then you will get 0 results — literally. That value is persisted, as it should be, between restarts of SQLYog, restarts of the PC SQLYog is running on, and, it turns out, even upgrades to SQLYog.

Don't set the limit to 0, or it will return 0 reults, quite happily. I won't bother to suggest that maybe a value of 0 in that field should result in an alert to the user, as what's the point of a table data tab that returns 0 results all the time, everytime. The reason I won't suggest that is because I'd really like to put this whole thing behind me and pretend I didn't ever start this post.

The reason it ocassionally would report data and ocassionally not, is because I would ocassionally just copy and paste the SQL command from the history tab, and other times I would type it in manually, not feeling the need to type the extra — and quite retarded — “limit 0” qualifier on the end.

So, hope this helps someone sometime!

Thanks again for the help,

Later,

-Patrick (JARU: Just Another Retarded User)

[peterlaursen]

hehe 😀

actually “0” in commonly used in configuration files meaning 'no limits', but not here!

[Author]

Posts