Re: [BUGS] Problem with COPY in 8.0.3

2005-10-18 Thread Oliver Elphick
On Wed, 2005-10-12 at 19:28 -0400, Tom Lane wrote: > Oliver Elphick writes: > > On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote: > >> Hm. Could we see the actual pg_attribute data for both this table and > >> its parent? > > > Here you are: > > Thanks. Nothing particularly strange-looking th

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 07:28:37PM -0400, Tom Lane wrote: > Oliver Elphick writes: > > On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote: > >> Hm. Could we see the actual pg_attribute data for both this table and > >> its parent? > > > Here you are: > > Thanks. Nothing particularly strange-loo

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Tom Lane
Oliver Elphick writes: > On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote: >> Hm. Could we see the actual pg_attribute data for both this table and >> its parent? > Here you are: Thanks. Nothing particularly strange-looking there though. Do you want to try tracing through COPY with a debugge

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Oliver Elphick
On Wed, 2005-10-12 at 17:45 -0400, Tom Lane wrote: > Oliver Elphick writes: > > ... in this particular case, the column > > order was wrong. I should add that the table inherits from another one, > > but the swapped columns are a long way into the extra columns specific > > to this table. > > Hm

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Tom Lane
Oliver Elphick writes: > ... in this particular case, the column > order was wrong. I should add that the table inherits from another one, > but the swapped columns are a long way into the extra columns specific > to this table. Hm. Could we see the actual pg_attribute data for both this table

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Tom Lane
Michael Fuhr <[EMAIL PROTECTED]> writes: > On Wed, Oct 12, 2005 at 08:23:15PM +0100, Oliver Elphick wrote: >> I actually use CURRENT_DATE; that is what the system turns it into. > Ah yes, I see that now. I generally use now(), so I hadn't noticed > that CURRENT_DATE and CURRENT_TIMESTAMP become '

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 08:17:23PM +0100, Oliver Elphick wrote: > On Wed, Oct 12, 2005 at 12:19:41PM -0600, Michael Fuhr wrote: > > Could you post the table definitions? > > Here it is: I created the tables you posted (sans foreign key constraints because you didn't include the referenced tables

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 08:23:15PM +0100, Oliver Elphick wrote: > On Wed, 2005-10-12 at 12:13 -0600, Michael Fuhr wrote: > > On another note, regarding the following: > > > > > invdate | date | not null default > > > ('now'::text)::date > > > taxpoint | date

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Oliver Elphick
On Wed, 2005-10-12 at 12:37 -0600, Michael Fuhr wrote: > On Wed, Oct 12, 2005 at 12:19:41PM -0600, Michael Fuhr wrote: > > On Wed, Oct 12, 2005 at 07:08:20PM +0100, Oliver Elphick wrote: > > > I should add that the table inherits from another one, but the > > > swapped columns are a long way into t

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 12:19:41PM -0600, Michael Fuhr wrote: > On Wed, Oct 12, 2005 at 07:08:20PM +0100, Oliver Elphick wrote: > > I should add that the table inherits from another one, but the > > swapped columns are a long way into the extra columns specific to > > this table. > > Could you pos

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 07:08:20PM +0100, Oliver Elphick wrote: > I should add that the table inherits from another one, but the > swapped columns are a long way into the extra columns specific to > this table. Could you post the table definitions? -- Michael Fuhr ---(en

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Michael Fuhr
On Wed, Oct 12, 2005 at 09:09:05AM +0100, Oliver Elphick wrote: > Pg 8.0.3 (Debian package) on AMD64, linux 2.6.12 > > I am importing a table using COPY. The data is tab-delimited. COPY > seems to be putting the data for one field into the preceding field, > which should contain the empty string

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Oliver Elphick
On Wed, 2005-10-12 at 13:52 -0400, Tom Lane wrote: > Oliver Elphick <[EMAIL PROTECTED]> writes: > > Pg 8.0.3 (Debian package) on AMD64, linux 2.6.12 > > I am importing a table using COPY. The data is tab-delimited. COPY > > seems to be putting the data for one field into the preceding field, > >

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Tom Lane
Oliver Elphick <[EMAIL PROTECTED]> writes: > Pg 8.0.3 (Debian package) on AMD64, linux 2.6.12 > I am importing a table using COPY. The data is tab-delimited. COPY > seems to be putting the data for one field into the preceding field, > which should contain the empty string. Can't reproduce that

Re: [BUGS] Problem with COPY in 8.0.3

2005-10-12 Thread Oliver Elphick
On Wed, 2005-10-12 at 09:09 +0100, Oliver Elphick wrote: > Pg 8.0.3 (Debian package) on AMD64, linux 2.6.12 > > I am importing a table using COPY. The data is tab-delimited. COPY > seems to be putting the data for one field into the preceding field, > which should contain the empty string. To f