From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Feature discussion: Should syntax errors abort a transaction? |
Date: | 2012-06-19 14:04:26 |
Message-ID: | 20120619135627.GA34283@crankycanuck.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jun 19, 2012 at 03:35:19PM +0200, Rafal Pietrak wrote:
>
> The point is, that SQL syntax errors are so obviusly different from
> execution errors, that noting this distinction should not raise any
> ambiguity.
Good. One looks forward to your fully-worked-out AI/ESP patch that gets
this right every time. While you're at it, I suggest fixing these
"obvious" mistakes:
SELECT SELECT 'text';
SELECT 'text;
SELECT INSERT 'text' INTO column;
INSERT 'text' INTO 'column';
And so on. Every one of these is a boiled down example of a stupid
think-o I have made more than once. This is what the command buffer
is for.
If you really want your input system to provide fairly complete syntax
checking for you, however, I will point out that psql's \e command
will happily drop you into the editor of your choice. If you want an
editor that knows more about what you want than you do, I think you
will find it is spelled "emacs".
Best,
A
--
Andrew Sullivan
ajs(at)crankycanuck(dot)ca
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-19 14:07:54 | Re: Feature discussion: Should syntax errors abort a transaction? |
Previous Message | Adrian Klaver | 2012-06-19 13:58:43 | Re: Error message "psql: could not connect to server: No such file or directory" |