From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | fabriziomello(at)gmail(dot)com, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal or just idea for psql - show first N rows from relation backslash statement |
Date: | 2013-02-14 14:24:35 |
Message-ID: | CAHyXU0xUnHsOu3oh0G2yjwCdoLVmBMkCo0e3GwgnX1a0XaN5gg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 14, 2013 at 1:25 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> few year ago I proposed a implementation of macros - and I wrote a
> prototype - enhanced psql
>
> http://okbob.blogspot.cz/search?q=epsql
>
> but now I don't think so enhancing psql in this direction is good way.
> Enhanced console needs creating from scratch - it should be based on
> some interpret language - LUA or javascript - probably it can be
> better integrated to modern UI, can better do autocomplete - and this
> design is out of my time possibilities and out of my targets.
The main argument against psql macros II guess is that if you want
bash like features, well, use bash.
For my part I think that whenever psql enhancements are brought up the
first think to consider is 'should this functionality exist on the
server side'. With proper stored procedures we get to write our own
stuff like:
CALL top10('foo');
which seems more general and just as terse. So I think implementing
call syntax is probably topping my 'wanted feature' list.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-02-14 14:33:51 | Re: proposal or just idea for psql - show first N rows from relation backslash statement |
Previous Message | Manlio Perillo | 2013-02-14 14:23:15 | [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite) |