[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)

[Author]

Posts