Okay,
Because I'm hardheaded as well as anxious to implement my own ideas
for the challenge of it :) ...
I've extended the the -t/--table option to optionally accept a WHERE
clause expression following the table pattern.
The user can, for example, run:
pg_dump -t "tab1:col1>15" -t "tab
On Sun, 2008-06-01 at 22:19 -0400, Stephen Frost wrote:
>
> or so. I suppose it might be interesting to consider an 'insert-format'
> output for COPY, which pg_dump could possibly be refactored to use when
> requested. It'd be nice if it was easier to have COPY support more
> formats but right
On Sun, 2008-06-01 at 22:02 -0400, Stephen Frost wrote:
> * Davy Durham ([EMAIL PROTECTED]) wrote:
> > To reiterate, it is not possible to use the COPY command to create
> > standard SQL INSERT statements that can be conveniently loaded by
> > another db. No?
>
> Erm, t
On Sun, 2008-06-01 at 20:53 -0400, Stephen Frost wrote:
> * Davy Durham ([EMAIL PROTECTED]) wrote:
> > The code is not all that much to maintain as it is, and making it an
> > addition to an existing parameter instead of a new one may not increase
> > the code size by much
On Sun, 2008-06-01 at 15:47 -0400, Tom Lane wrote:
> Davy Durham <[EMAIL PROTECTED]> writes:
> > So, if this patch is not acceptable as-is, what would you feel about
> > this:
> > I could enhance the -t/--table=NAME option to accept more than a
> >
On Sun, 2008-06-01 at 10:43 -0400, Tom Lane wrote:
> Davy Durham <[EMAIL PROTECTED]> writes:
> > I have added a new parameter, -w/--where=EXPR
> > This lets you specify an expression that will be used in a WHERE
> > clause when the data is dumped.
>
> Thi
Greetings,
I have developed a fairly simple patch to the pg_dump utility. It is
against version 8.3.1 source code.
I have added a new parameter, -w/--where=EXPR
This lets you specify an expression that will be used in a WHERE
clause when the data is dumped.
I have implemented and test
