Re: Proposal for psql wildcarding behavior w/schemas

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Alvaro Herrera <alvherre(at)atentus(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal for psql wildcarding behavior w/schemas
Date: 2002-08-06 15:58:46
Message-ID: Pine.LNX.4.21.0208061656580.3235-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 6 Aug 2002, Alvaro Herrera wrote:

> Nigel J. Andrews dijo:
>
> > Hmm...that's not how I've always understood shell quoting, at least for bash:
> >
> > ~$ aa=3
> > ~$ perl -e 'print join(",",@ARGV), "\n";' "1 $aa 2 3" 4 5 6
> > 1 3 2 3,4,5,6
> > ~$
>
> What's the difference? What your example is saying basically is that
> the shell is treating the "1 $aa 2 3" as a single parameter (i.e. spaces
> do not have the usual parameter-separating behaviour), _but_ variables
> are interpreted. Using '' prevents variable substitution, so
>
> > ~$ perl -e 'print join(",",@ARGV), "\n";' '1 $aa 2 3' 4 5 6
>
> should give
> 1 $aa 2 3,4,5,6

Oops, I've just realised the original was about glob expansion whereas I was
looking at other special characters.

--
Nigel J. Andrews
Director

---
Logictree Systems Limited
Computer Consultants

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2002-08-06 16:16:31 Re: CVS sources doesn't compiles
Previous Message Alvaro Herrera 2002-08-06 15:53:52 Re: Proposal for psql wildcarding behavior w/schemas