| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel T(dot) Staal" <DStaal(at)usa(dot)net> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: cannot remove column + no error msg |
| Date: | 2006-12-11 16:11:47 |
| Message-ID: | 12858.1165853507@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Daniel T. Staal" <DStaal(at)usa(dot)net> writes:
> On Mon, December 11, 2006 10:11 am, Bram Kuijper said:
>> Second question is related to that. If I type any bogus (e.g.
>> "sflkjdslkfj") onto the psql commandline, PostgreSQL remains silent.
> More related than you think, probably...
> An SQL statement is terminated by a semicolon, and nothing else. Until
> the statement is ended, there is no error. I bet if you type bogus
> characters into psql and finish with a ; it will give you an error.
Also, backslash commands take a different path --- it's possible to
execute \d for example while psql still thinks it's accumulating a
multi-line SQL command to send when it finally sees a semicolon.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bradley Russell | 2006-12-11 16:26:49 | delete cascade question |
| Previous Message | Daniel T. Staal | 2006-12-11 15:55:20 | Re: cannot remove column + no error msg |