Shooter7119 / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Export table as SQL dump, displays proper custom filename but exported file name wrong #1851

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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.

Original issue reported on code.google.com by kcros...@gmail.com on 13 Nov 2013 at 3:12

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
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'

Original comment by kcros...@gmail.com on 13 Nov 2013 at 3:37

GoogleCodeExporter commented 9 years ago
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.

Original comment by kcros...@gmail.com on 13 Nov 2013 at 3:41