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.
> This is nice in some cases, but is there a way to let it do some error
> checking on the bogus I type? I am not used to commandlines that just
> swallow text and don't warn for any errors, giving me the idea that the
> it is apparently correct. Anybody any idea to change some configuration
> parameters?
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.
Daniel T. Staal
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------