Re: [HACKERS] backslash in psql output

From: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
To: maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian)
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane), hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] backslash in psql output
Date: 1998-10-11 04:40:24
Message-ID: m0zSDIu-0000emC@druid.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thus spake Bruce Momjian
> OK, let's keep the removal of backslashes. Can you recommend a nice
> NULL display, perhaps '[NULL]' or '<NULL>'?

I'd like to make at least one vote to keep the status quo. Some of
us have come to depend on the existing behaviour. At least make
it an option that you have to turn on.

--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Taral 1998-10-11 04:51:58 RE: [HACKERS] postmaster locking issues.
Previous Message Billy G. Allie 1998-10-11 03:16:01 PostgreSQL 6.4 patches - portability related.