Re: failure and silence of SQL commands

From: Robert Poor <rdpoor(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: failure and silence of SQL commands
Date: 2011-04-28 19:22:59
Message-ID: BANLkTimnw0zh8pCn7q4UFraePn1HxecxdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message John Payne 2011-04-28 19:28:12 failure and silence of SQL commands
Previous Message Leif Biberg Kristensen 2011-04-28 18:41:18 Re: failure and silence of SQL commands