Re: pg_dump feature request: Exclude tables?

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: Glen Parker <glenebob(at)nwlink(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump feature request: Exclude tables?
Date: 2004-08-19 10:04:18
Message-ID: 1092909858.19834.30.camel@braydb
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2004-08-18 at 20:11, Glen Parker wrote:
> > >Hmm, while you're at it, maybe you could make it accept wild
> > >cards or regexp or something :-) That should allow you to toss
> > >the -n parameter altogether (schema.*) if you wanted to.
> > >
> > >It would also be at least as good, IMO, to accept only one -t
> > >option, re-defined as a comma-seperated list of names... And an
> > >exlusion parameter defined the same way.
> > >
> > How would this interact with the shell? It seems like a supportability
> > issue if we have to require single quotes around such arguments.
>
> I think wild cards would be extremely useful, but you're right, it can't be
> required for common cases. Maybe "-t schema." could be shorthand for "-t
> schema.*".

Anyone who uses shell commands must already be familiar with the need to
quote wildcard characters which are not meant for the shell. One major
utility which requires this is find; others that spring to mind are dpkg
-l and mmv. Anyone who doesn't get it will very soon be educated; I
don't see this issue as a reason not to use such wildcards.

Oliver Elphick

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oliver Elphick 2004-08-19 10:14:20 Re: libpq: passwords WAS: scripting & psql issues
Previous Message Daniel Martini 2004-08-19 10:00:01 Re: Pass parameters to SQL script