Re: psql Feature request \set query - Mailing list pgsql-hackers

From Greg Stark
Subject Re: psql Feature request \set query
Date
Msg-id E332EE0A-43D1-4E9F-A971-8AC8A1013560@enterprisedb.com
Whole thread Raw
In response to Re: psql Feature request \set query  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql Feature request \set query
List pgsql-hackers
For making psql fully scriptable I would think it would be smarter to  
embed a full well-supported existing language rather than trying to  
invent a new one.

If we do want to to that I would suggest looking at lua which is  
intended to be used this way.

greg

On 23 Oct 2008, at 05:45 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Joshua Drake <jd@commandprompt.com> writes:
>> "Robert Haas" <robertmhaas@gmail.com> wrote:
>>> "We can't do anything unless we do everything" is a recipe for
>>> failure.
>
>> True enough, but a car doesn't roll without at least four wheels.
>
> Perhaps more to the point: you don't have to implement every part of a
> set of features at the same time, but it's a good idea to design them
> all together.  Else you risk writing something that doesn't play nice
> with the other parts; and by the time you find out, it's too late to
> change without creating a backwards-compatibility problem.
>
>            regards, tom lane
>
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers


pgsql-hackers by date:

Previous
From: "Charles Duffy"
Date:
Subject: Re: Making pg_standby compression-friendly
Next
From: Magnus Hagander
Date:
Subject: Re: psql Feature request \set query