MySQL Bugs: #7732: Can't Execute queries

Bug #7732	Can't Execute queries
Submitted:	7 Jan 2005 16:15	Modified:	7 Jan 2005 17:14
Reporter:	Jorge Quevedo	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Windows (Win XP Pro SP2)
Assigned to:		CPU Architecture:	Any

Description:
Upgraded from 1.1.2 to 1.1.5 in two machines running XP pro Sp2 and on neither one I can execute any queries, either by clicking on the UI button or by Ctrl-Enter or by Ctrl-Shift-Enter. None of the bookmarked queries work either. 

I am using it to connect to a 3.23 database.

How to repeat:
upgrade a 1.1.2 distribution to a 1.1.5
It connects to the database with out problems (I can see all the schemas)

I wasn't able to repeat on XP SP2. However when I upgrade for new
version I uninstall first the older one via Panel Control and the install
the new version.

I too am having problems with this (related bug #7736).  I noticed on the bottom of the browser a message shows:

A MySQL error was encountered. The message is: Cannot fetch table information. The following error occurred: Lost connectio

I'm sure the last word should be connection, but I can't find a way to view the rest of the message, if it does continue.

On my website, however, the connection is fine and is connecting through the same two computers.  Apparently, ColdFusion can see these schemas and tables, but the Browser can't.  Do I have a setting wrong?

I think I just found out what my problem was, although this could lead to a new
bug...

I installed QB on the database server itself, and was immediately able to view
schemas and edit the records.  I'm guessing that you cannot edit records from a
remote server/computer, as that was my problem.

Note: I posted this on the other bug I mentioned above, but feel it relates to this issue (as they give the same problem, almost).

When I reported my problem, the Query Browser was installed in a remote machine connecting to a 3.23 server on a Linux machine.

Did you try installing it directly on the Linux server?  Or do you not have access to it?  If it does work on your Linux server, that could pinpoint the problem.

By the way, I'm using 4.0.12-nt on our production DB server (to be replaced soon) and 4.0.18-nt on our testing DB server, both running Windows Server 2000, while my testing application server (trying to make the connection) is running Windows Server 2003.