Re: COPY BINARY is broken... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: COPY BINARY is broken...
Date
Msg-id 17592.976487667@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY BINARY is broken...  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>>>> Its handling of nulls is bizarre, too.  I'm thinking this might be a
>>>> good time to abandon backwards compatibility and switch to a format
>>>> that's a little easier to read and write.  Does anyone have an opinion
>>>> pro or con about that?
>> 
>> BINARY COPY scared the bejeezus out of me, anyone using the interface
>> is asking for trouble and supporting it seems like a nightmare, I
>> would rip it out.

> Tom, just keep in mind that the format is documented in copy.sgml.

Not documented *correctly*, I notice.  There are at least two errors,
plus the rather major omission that <tuple data> is not explained.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: memory management suggestion
Next
From: Bruce Momjian
Date:
Subject: Re: Re: COPY BINARY file format proposal