From: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY formatting |
Date: | 2004-03-18 08:04:07 |
Message-ID: | 20040318080407.GC19093@zf.jcu.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 18, 2004 at 07:48:40AM +0100, Karel Zak wrote:
> On Wed, Mar 17, 2004 at 11:02:38AM -0500, 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.
>
> Why? I said it's pseudo code. It should use standard fmgr API like
> every other PostgreSQL function or is it problem and I overlook
> something? It must to support arbitrary programming language and not
> C only.
Well, I look over the COPY code and best will start with hardcoded
version, but make it modular in code and if all will right we can think
about some interface for others formats definition. OK?
It's pity that main idea of current COPY is based on separated lines
and it is not more common interface for streaming data between FE and BE.
Karel
--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Kindness | 2004-03-18 09:29:03 | COPY formatting |
Previous Message | Karel Zak | 2004-03-18 06:53:45 | Re: COPY formatting |