Tom Lane wrote:
> "hernan gonzalez" <[EMAIL PROTECTED]> writes:
> > test=# create view vchartest as
> >  select encode(convert_to(c,'LATIN9'),'escape') as c1 from chartest;
> 
> Hmm.  This isn't a very sensible combination that you've written here,
> but I see the point: encode(..., 'escape') is broken in that it fails
> to convert high-bit-set bytes into \nnn sequences.  At least in
> multibyte backend encodings, we *must* do that to produce valid textual
> output.  I suspect that for consistency we should do it regardless of
> backend encoding.

With Tom's encoding() patch applied I assume there is no TODO item here.

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to