From: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Joshua Drake <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql Feature request \set query |
Date: | 2008-10-23 07:02:32 |
Message-ID: | E332EE0A-43D1-4E9F-A971-8AC8A1013560@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Joshua Drake <jd(at)commandprompt(dot)com> writes:
>> "Robert Haas" <robertmhaas(at)gmail(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-10-23 07:13:40 | Re: psql Feature request \set query |
Previous Message | Charles Duffy | 2008-10-23 06:54:41 | Re: Making pg_standby compression-friendly |