Re: \Copy and "Copy With Headers" -- every day these bug me. - Mailing list pgadmin-support

From Guillaume Lelarge
Subject Re: \Copy and "Copy With Headers" -- every day these bug me.
Date
Msg-id 1330035334.19409.1.camel@localhost.localdomain
Whole thread Raw
In response to Re: \Copy and "Copy With Headers" -- every day these bug me.  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-support
On Tue, 2012-02-21 at 23:25 +0100, Guillaume Lelarge wrote:
> On Mon, 20 Feb 2012 21:11:17 +0100, Guillaume Lelarge
> <guillaume@lelarge.info> wrote:
> > 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've made more progress tonight. Now, the user can select which columns in
> the table will be filled (of course, the file should only contain these
> columns). He can also select which columns will be ignored for the NULL
> string.
> 
> New screenshots at http://developer.pgadmin.org/~guillaume/importtool/
> 
> I'm now wondering if I should add a SQL tab, to show the query before it
> gets executed.
> 
> Seems it's almost ready to get commited.
> 
> Comments welcomed.
> 

No comments, so I commited the patch (actually with a few fixes that I
think were required).

The import tool will be available with 1.16.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com



pgadmin-support by date:

Previous
From: Colin Beckingham
Date:
Subject: Panel height redimensioning in Query builder
Next
From: Colin Beckingham
Date:
Subject: Error "column not found in pgSet: current_query"