Обсуждение: COPY..FROM question on 7.3

Поиск
Список
Период
Сортировка

COPY..FROM question on 7.3

От
"Patrick Hatcher"
Дата:
Trying to import a 4 column tab delimited file into Pg 7.3.  As it stands,
the last line contains only the first two columns.  I would expect that the
import would only update the first two column like it did in  Pg 7.2.x.
However, I get an error message Missing data from column "X".
Is there something I can do to avoid the message?
TIA

Patrick Hatcher
Macys.Com
Legacy Integration Developer




Re: COPY..FROM question on 7.3

От
Tom Lane
Дата:
"Patrick Hatcher" <PHatcher@macys.com> writes:
> Trying to import a 4 column tab delimited file into Pg 7.3.  As it stands,
> the last line contains only the first two columns.  I would expect that the
> import would only update the first two column like it did in  Pg 7.2.x.
> However, I get an error message Missing data from column "X".
> Is there something I can do to avoid the message?

Yes, fix the data file ;-).  This was deliberately tightened in 7.3 to
detect the sorts of obscure mistakes that the old behavior allowed to
slip by ...

            regards, tom lane

Re: COPY..FROM question on 7.3

От
"Patrick Hatcher"
Дата:
Unfortunately, I thought that was what you were going to say.  Time to pull
out the PERL scripts
Thanks

Patrick Hatcher
Macys.Com





                    Tom Lane
                    <tgl@sss.pgh.p       To:     "Patrick Hatcher" <PHatcher@macys.com>
                    a.us>                cc:     pgsql-general@postgresql.org
                                         Subject:     Re: [GENERAL] COPY..FROM question on 7.3
                    01/29/2003
                    04:01 PM






"Patrick Hatcher" <PHatcher@macys.com> writes:
> Trying to import a 4 column tab delimited file into Pg 7.3.  As it
stands,
> the last line contains only the first two columns.  I would expect that
the
> import would only update the first two column like it did in  Pg 7.2.x.
> However, I get an error message Missing data from column "X".
> Is there something I can do to avoid the message?

Yes, fix the data file ;-).  This was deliberately tightened in 7.3 to
detect the sorts of obscure mistakes that the old behavior allowed to
slip by ...

                               regards, tom lane