[pgadmin-support] Improper CSV export delimiter
Bug report: When I use File > Export from a Query window, it's clearly trying to make a CSV. The suggested filename is suffixed with .csv. The problem is the semicolon character is selected by default. That is not CSV. Please change this so the comma is the default delimiter. Now, I understand semicolon is the standard in certain regions (e.g., France?), but the vast majority of cases, comma is the norm. If semicolon is selected by default, it should only be because regional OS settings are detected that recommend this. Aren
Re: [pgadmin-support] Improper CSV export delimiter
On 6 November 2010 21:08, Aren Cambre wrote: > Bug report: > > When I use File > Export from a Query window, it's clearly trying to make a > CSV. The suggested filename is suffixed with .csv. > Are you sure that isn't just there because that's the last filename you used? Mine doesn't default to anything. If I click on the ellipsis and type a filename without an extension into the file browser and click OK, it just comes up with the path and the filename I typed without an extension. -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935
Re: [pgadmin-support] Improper CSV export delimiter
Le 06/11/2010 22:19, Thom Brown a écrit : > On 6 November 2010 21:08, Aren Cambre wrote: > >> Bug report: >> >> When I use File > Export from a Query window, it's clearly trying to make a >> CSV. The suggested filename is suffixed with .csv. >> > > Are you sure that isn't just there because that's the last filename you > used? Mine doesn't default to anything. If I click on the ellipsis and type > a filename without an extension into the file browser and click OK, it just > comes up with the path and the filename I typed without an extension. > +1 More to the point, all this dialog knows is that you want to export data. It doesn't know what CSV is. If your file is suffixed with .csv, .txt, .xls, ., it doesn't care. It doesn't know what this suffix means. It doesn't even know that it could mean something. So, right now, it cannot pre-select specific items that should be related with your file suffix. Moreover, the value you have as a column separator comes from your last export. You probably set it to a semi-colon the last time you used the Export functionality. Anyway, it would be a really good thing to "beautify" this dialog. It's actually really horrible. And maybe, while we are at it, we could add this kind of functionality. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] saved passwords deleted
Le 05/11/2010 17:18, Michael Shapiro a écrit : > I noticed that if I have a problem connecting to a server for which I have a > saved password, the entry in pgpass.conf is deleted. > When I later succeed in connecting, the server then prompts for a password > (and the pgpass.conf entry is added back). > > Is it possible to not delete the entry if the connection fails? > Right now, no. And I can't find this dialog now, must be too tired. But, yes, it could probably be a good idea to add such an option. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] Improper CSV export delimiter
Maybe. But if I click on the ellipsis, the Windows dialog has CSV preselected in *Save as type*, even if the prior extension isn't CSV. But even more strongly, all the settings on the *Export data to file* dialog are CSV-compliant except that one. Shouldn't common standards be the default? What value is there in being "almost" CSV vs. being truly CSV? The problem with this is when you save a CSV with semicolons instead of commas, other programs may not recognize the file. Already ran into a problem importing into Excel with semicolon separations. So if I forget change to comma, I may end up doing an export and may risk a complex CSV edit later. (It's simple if you're just replacing *";"* with *","* but can be complex in certain scenarios.) Aren On Sat, Nov 6, 2010 at 4:19 PM, Thom Brown wrote: > On 6 November 2010 21:08, Aren Cambre wrote: > >> Bug report: >> >> When I use File > Export from a Query window, it's clearly trying to make >> a CSV. The suggested filename is suffixed with .csv. >> > > Are you sure that isn't just there because that's the last filename you > used? Mine doesn't default to anything. If I click on the ellipsis and type > a filename without an extension into the file browser and click OK, it just > comes up with the path and the filename I typed without an extension. > > -- > Thom Brown > Twitter: @darkixion > IRC (freenode): dark_ixion > Registered Linux user: #516935 >
Re: [pgadmin-support] Improper CSV export delimiter
> > Moreover, the value you have as a column separator comes from your last > export. You probably set it to a semi-colon the last time you used the > Export functionality. > This was the first time I ever used the dialog. Aren
