Skip site navigation (1) Skip section navigation (2)

Re: COPY BINARY is broken...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Alfred Perlstein <bright(at)wintelcom(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY BINARY is broken...
Date: 2000-12-10 20:52:16
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > 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.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: mlwDate: 2000-12-10 21:31:20
Subject: Functions returning sets, last one I promise!
Previous:From: Bruce MomjianDate: 2000-12-10 20:34:22
Subject: Re: memory management suggestion

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group