Skip site navigation (1) Skip section navigation (2)

Re: character problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: character problem
Date: 2005-10-12 23:02:31
Message-ID: 5056.1129158151@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Mon, Oct 10, 2005 at 10:27:27AM -0400, Tom Lane wrote:
>> No, SQL_ASCII represents the complete absence of any encoding
>> knowledge.  With this database setting, changing client_encoding is a
>> complete no-op.  Postgres will just absorb and re-emit strings exactly
>> as they were supplied originally, no matter what client_encoding is.

> The documents remain pretty confusing about this, assuming I still
> understand the current state of affairs (always a dangerous
> assumption).  The chart in
> <http://developer.postgresql.org/docs/postgres/multibyte.html>, for
> instance, says "SQL_ASCII" supports "ASCII".  I'm not sure what to do
> about this (I've noticed it before, and run into the same quandary).

You're right, the documentation basically doesn't explain this at all :-(
I'll try to add something.

			regards, tom lane

In response to

pgsql-admin by date

Next:From: Walter KaanDate: 2005-10-12 23:14:24
Subject: Re: front end application
Previous:From: Andrew SullivanDate: 2005-10-12 21:26:42
Subject: Re: character problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group