Re: \Copy and "Copy With Headers" -- every day these bug me.
От | Guillaume Lelarge |
---|---|
Тема | Re: \Copy and "Copy With Headers" -- every day these bug me. |
Дата | |
Msg-id | 38ba5b53f2993e1746142b89ce7b2df4@localhost обсуждение исходный текст |
Ответ на | Re: \Copy and "Copy With Headers" -- every day these bug me. (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: \Copy and "Copy With Headers" -- every day
these bug me.
|
Список | pgadmin-support |
On Mon, 20 Feb 2012 09:15:07 +0000, Dave Page <dpage@pgadmin.org> wrote: > On Mon, Feb 20, 2012 at 7:31 AM, Guillaume Lelarge > <guillaume@lelarge.info> wrote: >> Hi Ashesh, >> >> On Mon, 2012-02-20 at 10:20 +0530, Ashesh Vashi wrote: >>> [...] >>> I think - we should have some default values in some text controls. >>> i.e. Delimiter, Quote, Escape >>> >> >> We can do exactly like the frmExport window: replacing text control with >> combobox. Comboboxes will have some usual values (like tab, comma, etc >> for delimiter), but offer the possibility to change them by anything a >> user would like. > > +1 > This is done. >> I was also wondering if this window should offer a way to export the >> contents of a table (in which case, it would also be available for >> foreign tables, and views). > > We already have frmExport for that. That could probably be extended > fairly easily to be a context menu option for tables and views etc, as > well as working off the SQL Query tool. Not easily, at least if we want to use the COPY API. Right now, frmExport exports a grid or a set (pgSet). I want to avoid using a set because it means we would have to execute a SELECT. I much prefer using COPY with all its features. Anyway, noone seems interested, so I guess it won't be done. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
В списке pgadmin-support по дате отправления: