Re: Proposal for psql wildcarding behavior w/schemas - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Proposal for psql wildcarding behavior w/schemas
Date
Msg-id Pine.LNX.4.44.0208061149380.5069-100000@cm-lcon1-46-187.cm.vtr.net
Whole thread Raw
In response to Re: Proposal for psql wildcarding behavior w/schemas  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
Responses Re: Proposal for psql wildcarding behavior w/schemas  ("Nigel J. Andrews" <nandrews@investsystems.co.uk>)
List pgsql-hackers
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

-- 
Alvaro Herrera (<alvherre[a]atentus.com>)
FOO MANE PADME HUM



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Better handling of parse errors
Next
From: "Nigel J. Andrews"
Date:
Subject: Re: Proposal for psql wildcarding behavior w/schemas