Re: failure and silence of SQL commands - Mailing list pgsql-novice

From Robert Poor
Subject Re: failure and silence of SQL commands
Date
Msg-id BANLkTimnw0zh8pCn7q4UFraePn1HxecxdA@mail.gmail.com
Whole thread Raw
In response to Re: failure and silence of SQL commands  (Leif Biberg Kristensen <leif@solumslekt.org>)
List pgsql-novice
@Lief, @Tom: Good points (especially 'and John's not exactly the first
person to forget a semicolon.' ;)

Part of the problem may be that 'postgres=#' and 'postgres-#' look
mighty similar.  If so, a simple fix would be to change PROMPT2 from
'%/%R%# ' to '%R%# ', that is, make a toplevel prompt show the
database name:

    postgres=#

and drop the database name in the 'continuation' prompt:

    -#

which would make it a lot more obvious that it's waiting for input.
John (et al) -- what do you think?

- r

pgsql-novice by date:

Previous
From: Leif Biberg Kristensen
Date:
Subject: Re: failure and silence of SQL commands
Next
From: "John Payne"
Date:
Subject: failure and silence of SQL commands