Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=1851
Reporter: kcrossen Date: 2013-11-13
What steps will reproduce the problem?
1.Right click table, Export > As SQL dump...
2.Expand Customize Filename
3.xxx- (database) - (table) - (year) (month) (day)
4. Customized filename displays as: 'xxx-mydb-mytable-20131113.sql'
5. Actual saved file is: 'xxx-mydb--20131113.sql'
What version of Sequel Pro are you using? 1.0.2
What version of OS X are you using? 10.8 (Mountain Lion)
What version of MySQL are you connecting to on the server? 5.5
Please provide any additional information below.
Author: kcrossen Date: 2013-11-13
Subsequent export as csv creates file w/ correct name. 'xxx-mydb-mytable-20131113.csv'
Now, exit export dialog, right-click different table, export > as sql, customized file name still displays as 'xxx-mydb-mytable-20131113.sql', should display as 'xxx-mydb-yourtable-20131113.sql', actually exports as 'xxx-mydb--20131113.sql' (i.e., missing table name)
Subsequent export as csv exported correctly as filename 'xxx-mydb-yourtable-20131113.csv'
Whatever table has been selected on modification of customize filename, that table name will always be displayed as part of the customized filename, regardless which file is actually being exported, even in the case of csv which does create a file w/ the proper name.
Closed, but has this been fixed? In vers 1.02 works properly when exporting CSV file, but still missing table name in filename when exporting SQL.
Yea, this still appears to be a problem; when exporting SQL the table name is omitted from the file name when saved to the filesystem.
Fix table name token not being used in SQL exports even when only one…
… table is selected (#1858)
Issue fixed in 1.1.1