From: | "John Payne" <jcpayne(at)uw(dot)edu> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: silence and failure of SQL commands |
Date: | 2011-04-28 21:28:20 |
Message-ID: | 005501cc05eb$32ce3510$986a9f30$@edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
One subtle aspect of this is that I did the same thing wrong several times
in a row:
1. I enter an SQL command without a semicolon. No response. (I fail
to notice the cursor change from => to ->)
2. I enter another SQL command without a semicolon. No response, and
this time, the cursor is already '->', so NOTHING changes.
3. I enter another SQL command without a semicolon.no response,
nothing changes.
4. Etc.
I don't know how useful it is to be able to split commands over many lines,
but maybe after you've hit Enter without a semicolon several times it could
give you more of a prompt.
John
From | Date | Subject | |
---|---|---|---|
Next Message | John Payne | 2011-04-28 22:57:59 | Re: silence and failure of SQL commands |
Previous Message | Robert Poor | 2011-04-28 21:17:17 | Re: silence and failure of SQL commands |