MySQL Bugs: #16438: Doesnt load the saved query when doubleclicked

Bug #16438	Doesnt load the saved query when doubleclicked
Submitted:	12 Jan 2006 7:29	Modified:	14 Nov 2006 16:26
Reporter:	Niekas	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.18	OS:	Windows (WindowsXP SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	Generic

Description:
Query browser doesnt load the saved query file when doubleclicked.

How to repeat:
Run Query Browser
Edit and save any query (save as file, for example query.dbquery)
Close Query browser
DoubleClick the query file (query.dbquery)

Thank you for a problem report. 

Why do you think that QB should be associated by default with such files (*.dbquery) on Windows? It may be reasonable for *.sql, but you can do it yourself, as for any other extension. So, I see no bug here.

Well, i did a default installation and it did associate QB with *.sql and *.dbquery files. In my case the files are associated with QB, and doubleclicking on the files the QB actually starts, but doesnt load the query from the file (i get empty query window).

Shouldn't i expect the file content to be loaded into the QB? (-;

Ok, maybe i explained not quite well where is the problem.

The problem is that QB doesnt load the content of associated file (doesnt matter, if the file is associated by default of manualy) when you doubleclick the file. When i click the *.doc files, the MsWord or OpenOffice starts, takes the clicked file name/path as parameter and loads the content of the file.

QB doesnt! It just starts and the query window is empty. This is definetely a bug (-;

QB is by default associated with *.sql and *.dbquery files. I pointed the *.dbquery file as an example, because by defualt QB saves files as *.dbquery.

Sorry, my fault. Verified just as described with 1.1.18 on XP. You can associate QB with any extension, and it opens, but file content is not loaded. So, this is either a bug or, at least, a reasonable feature request.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html