MySQL Bugs: #53731: Saving script is not taking file name the user want

Bug #53731	Saving script is not taking file name the user want
Submitted:	18 May 2010 7:26	Modified:	24 May 2010 14:28
Reporter:	Susanne Ebrecht	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:		OS:	Linux
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
1. Open Workbench
2. Open connection to start querying
3. fill some text
4. File -> Save Script
5. Name = foo
6. Goto shell and into the path where foo is saved
7. $ less foo

foo: No such file or directory

8. $ ls

You will figure out that Workbench not did what it should. The file is not named "foo" it is named "foo.sql".

We are living in 21st century and not anymore in 20th century.

This behaviour might be still familiar too some conservative Windows users but in Unix world this is a NOGO!!!

More weird:

Name the file "foo.txt". It will end on file system as foo.txt.sql.

This is ridiculous.

How to repeat:
See above

Problem of extra .sql extension being added for filenames with extension was fixed.
Default .sql extension being auto-added is a feature, not a bug

fix confirmed in repository.
linux version now doesn't automatically add a default file extension (as it seem to be standard on linux that way) while windows/osx add .sql if you don't define one

An entry has been added to the 5.2.22 changelog:

On Linux, MySQL Workbench automatically added a .sql extension, where an extension was not specified, to any script file saved from the SQL Editor.

MySQL Workbench has been changed so that on Linux a .sql extension is not automatically added. However, on Windows the file extension is added if one is not specified.