Re: [PATCHES] Current-stream read for psql's \copy - Mailing list pgsql-hackers

From Mark Feit
Subject Re: [PATCHES] Current-stream read for psql's \copy
Date
Msg-id 16425.9862.197028.645507@gargle.gargle.HOWL
Whole thread Raw
In response to Re: [PATCHES] Current-stream read for psql's \copy  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian writes:> > I will do it by vote, not because _I_ decide it is unintuitive.  And I> don't have to talk
_you_into it, just a majority of developers.
 

Well, here's my vote on the subject: I purposefully avoided changing
the existing behavior because (a) it would break something I will
still find useful after the patch (b) I really think STDIN should mean
STDIN just as /some/file means /some/file.

What precipitated the patch in the first place was a need to be able
to do copies in-line to populate tables with small amounts of initial
data.  I like that initial data to be neat, readable and easy to
browse/modify without having to mentally filter through a lot of
INSERTs.  I have an automated system that takes a bunch of directories
containing various things like table creation and strings them
together into large SQL scripts to build, clear and destroy a
database.  Previously, I was having to deliver multiple files for
database builds; now I can just deliver one that does everything.
                        - Mark
-- 
"DOS computers ... are by far the most popular, with about 70 millionmachines in use worldwide.  Macintosh fans ...
notethat cockroachesare far more numerous than humans, and that numbers alone do notdenote a higher life form."   --
NewYork Times, November 26, 1991
 



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Renaming tables to other schemas
Next
From: Rodrigo
Date:
Subject: Re: MS SQL features for new version