pgsql: On second thought, use an empty string instead of "none" when no

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: On second thought, use an empty string instead of "none" when no
Date: 2013-01-15 20:24:33
Message-ID: E1TvD3h-00005n-Ru@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On second thought, use an empty string instead of "none" when not connected.

"none" could mislead to think that you're connected a database with that
name. Also, it needs to be translated, which might be hard without some
context. So in back-branches, use empty string, so that the message is
(currently ""), which is at least unambiguous and doens't require
translation. In master, it's no problem to add translatable strings, so use
a different fix there.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/66debecd0c2a507500384a2eb727664f916780f8

Modified Files
--------------
src/bin/psql/help.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Kevin Grittner 2013-01-16 16:48:17 Re: Materialized views WIP patch
Previous Message Heikki Linnakangas 2013-01-15 17:26:52 pgsql: Don't pass NULL to fprintf, if not currently connected to a data