> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Let me ask a bigger question.  We have the length of the text string in
> > the varlena header.  Are we concerned about backend code not handling
> > NULL in text fields, or frontend code returning strings with embedded
> > nulls?
> 
> The former.
> 
> > I see problems in the text() functions for nulls, but is such a
> > limitation required for text types?
> 
> Unless you want to re-implement strcoll() and friends from scratch.

Yes, I saw strcoll().

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

• Re: Bytea/Base64 encoders for libpq - interested? at 2001-09-04 17:33:26 from Tom Lane

pgsql-hackers by date

Next:	From: Barry Lind	Date: 2001-09-04 17:40:36
	Subject: Re: [JDBC] Troubles using German Umlauts with JDBC
Previous:	From: Tom Lane	Date: 2001-09-04 17:33:26
	Subject: Re: Bytea/Base64 encoders for libpq - interested?

pgsql-patches by date

Next:	From: Joseph Shraibman	Date: 2001-09-04 20:56:28
	Subject: Patch for jdbc2 ResultSet.java
Previous:	From: Tom Lane	Date: 2001-09-04 17:33:26
	Subject: Re: Bytea/Base64 encoders for libpq - interested?