Re: COPY commands could use an enhancement.
От | Tom Lane |
---|---|
Тема | Re: COPY commands could use an enhancement. |
Дата | |
Msg-id | 15205.988645018@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | COPY commands could use an enhancement. (Alfred Perlstein <bright@wintelcom.net>) |
Ответы |
Re: COPY commands could use an enhancement.
Re: COPY commands could use an enhancement. Re: COPY commands could use an enhancement. Re: COPY commands could use an enhancement. |
Список | pgsql-hackers |
Alfred Perlstein <bright@wintelcom.net> writes: > It would be very helpful if the COPY command could be expanded > in order to provide positional parameters. I think it's a bad idea to try to expand COPY into a full-tilt data import/conversion utility, which is the direction that this sort of suggestion is headed in. COPY is designed as a simple, fast, reliable, low-overhead data transfer mechanism for backup and restore. The more warts we add to it, the less well it will serve that purpose. Example: if we allow selective column import, what do we do with missing columns? Must COPY now be able to handle insertion of default-value expressions? I think it'd be better to put effort into an external data translation utility that can deal with column selection, data reformatting, CR/LF conversion, and all those other silly little issues that come up when you need to move data from one DBMS to another. Sure, we could make the backend do some of this stuff, but it'd be more maintainable as a separate program ... IMHO anyway. I think that pgaccess and pgadmin already have some capability in this line, BTW. regards, tom lane
В списке pgsql-hackers по дате отправления: