| From: | "Pollard, Mike" <mpollard(at)cincom(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Cc: | <pgman(at)candle(dot)pha(dot)pa(dot)us>, <chriskl(at)familyhealth(dot)com(dot)au>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Different length lines in COPY CSV |
| Date: | 2005-12-12 15:15:03 |
| Message-ID: | 6418CC03D0FB1943A464E1FEFB3ED46B01B22118@im01.cincom.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> What's been suggested in the past is some sort of standalone
> file-format-conversion utility, which could deal with this sort of
stuff
> without having to also deal with all the backend-internal
considerations
> that COPY must handle. So (at least in theory) it'd be simpler and
more
> maintainable. That still seems like a good idea to me --- in fact,
> given my druthers I would rather have seen CSV support done in such an
> external program.
Why not add hooks into COPY to call the user's massage functions? That
way you don't have to read and write the data, then read it again to
load it into the database.
Mike Pollard
SUPRA Server SQL Engineering and Support
Cincom Systems, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-12-12 15:19:00 | Re: psql patch: new host/port |
| Previous Message | Bruce Momjian | 2005-12-12 15:11:12 | Re: Backslashes in string literals |