search

Shooter7119 / sequel-pro

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

[REQ] Save export path on a per-schema basis #1545

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently the export path is remembered as the last one used, irrespective of 
whether we are in the same schema as we were when the last export was made.

It would be nice to have the option to save the export path on a per schema 
basis, so that when switching from db1 after doing an export to db2 and going 
to export, you get the export path saved for db2, not db1

This is similar to issue 
http://code.google.com/p/sequel-pro/issues/detail?id=1126 but is perhaps a more 
flexible approach longer term. (The two are not mutually exclusive either, so 
both could be implemented for ultimate export flexibility)

-----------------------------------------
SP 1.0 RC1, OS X 10.7.5, MySQL 5.1.63-log

Original issue reported on code.google.com by jrouff...@gmail.com on 29 Jan 2013 at 2:47

GoogleCodeExporter commented 9 years ago 
Update:
It is also related (to some extent) to this requirement:
http://code.google.com/p/sequel-pro/issues/detail?id=153

Original comment by jrouff...@gmail.com on 29 Jan 2013 at 2:49