From: | expect <expect(at)ihubbell(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: importing db as text files |
Date: | 2003-08-15 07:53:03 |
Message-ID: | 20030815005303.17eb4c7d.expect@ihubbell.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 15 Aug 2003 00:32:01 -0700 (PDT)
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
>
> On Thu, 14 Aug 2003, expect wrote:
>
> > On Thu, 14 Aug 2003 12:46:07 -0500
> > Bruno Wolff III <bruno(at)wolff(dot)to> wrote:
> > > Note that it isn't obvious what empty strings should map to for numbers.
> > > NULL and 0 make about as much sense as using the default value.
> >
> > Well I'm new here but it seems to me they should map to the default value
> > for that column. Why wouldn't they?
>
> One problem with doing that is that it's inconsistent.
Please elaborate. How is it inconsistent, exactly?
>
> Given
> create table test(
> a text default 'abc',
> b int default 5
> );
>
> copy test from stdin with delimiter ',';
> ,
> \.
>
> What would you expect the values of the row in test
> to be?
Oh a test....
Does the \. end the STDIN input?
Where's the null option? Don't you mean:
copy test from stdin with delimiter ',' null '';
In this case I would expect the row to have:
a | b
----------
|
abc | 5
Is this too much to expect?
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2003-08-15 08:23:54 | Re: Resolved: PostGreSQL - Accessing It |
Previous Message | Stephan Szabo | 2003-08-15 07:33:59 | Re: [GENERAL] 7.4Beta |