Re: surppressing column names in COPY format
| От | Robert Treat |
|---|---|
| Тема | Re: surppressing column names in COPY format |
| Дата | |
| Msg-id | 1059686014.22273.1623.camel@camel обсуждение исходный текст |
| Ответ на | Re: surppressing column names in COPY format (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: surppressing column names in COPY format
|
| Список | pgsql-general |
On Thu, 2003-07-31 at 16:50, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > On Thu, 2003-07-31 at 15:18, Tom Lane wrote:
> >> I don't really agree that we've "lost functionality" here, though ---
> >> you might as well claim that it's a bug that the COPY command forces
> >> you to restore the data into a particular table.
>
> > By that logic then what is the point of allowing data dumped as INSERTS
> > both with and without column names?
>
> None; we just haven't gotten around to removing code that no longer
> pulls its weight. The no-column-name variant is just as dangerous as
> it was in the COPY case, IMHO.
>
by dangerous you mean functional right? (I'm not changing the data, just
the column name)
would a patch to remove this dead code (the insert without column case)
be accepted for 7.4?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
В списке pgsql-general по дате отправления: