Re: surppressing column names in COPY format
От | Robert Treat |
---|---|
Тема | Re: surppressing column names in COPY format |
Дата | |
Msg-id | 1059683609.22260.1617.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 15:18, Tom Lane wrote: > Robert Treat <xzilla@users.sourceforge.net> writes: > > the problem is that I am restoring the data to a database with different > > column names, which errors out in 7.3 (but didn't under 7.2 since it > > didn't produce column names in the COPY output). I checked the docs and > > it provided no clue as to how to suppress column names for COPY only > > dumps. > > I think you can still get it to dump as INSERTs without column names. that was an example table, the actual table has millions of rows, I need to use COPY on it. > > 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. If you need to do > data transformation (which includes relabeling columns IMHO), restore > the data into a temp table and then do INSERT ... SELECT ... to massage > it into what you want. > By that logic then what is the point of allowing data dumped as INSERTS both with and without column names? Obviously there is functionality to be gained (or lost) doing it with or without column names, and in the current case I'm not gaining anything by having the columns explicitly named, so a flag to turn them off would be handy. Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
В списке pgsql-general по дате отправления: