From: | Fernando Nasser <fnasser(at)redhat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY formatting |
Date: | 2004-03-17 16:11:18 |
Message-ID: | 405878A6.5060504@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
>
>> The formatting function API can be pretty simple:
>> text *my_copy_format(text *attrdata, int direction,
>> int nattrs, int attr, oid attrtype, oid relation)
>
>
> This seems like it could only reasonably be implemented as a C function.
> I can't really imagine the average user of COPY wanting to write C in
> preference to, say, an external perl script. What's the real use-case
> for the feature?
>
That is why I suggested providing a pre-written/pre-compiled/installed
function for CSV (call it CSV?). Advanced users could still write their
own as people can write many other things if they know their ways.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-17 16:36:59 | Re: [HACKERS] Index creation takes for ever |
Previous Message | Andrew Dunstan | 2004-03-17 16:06:34 | Re: COPY formatting |