From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: character problem
Date: Wed, 12 Oct 2005 17:26:42 -0400
Message-ID: <20051012212642.GA13571@phlogiston.dyndns.org> (raw)
In-Reply-To: <20560.1128954447@sss.pgh.pa.us>
References: <4349106C.6080206@infinito.it>
<did562$epf$1@news.hub.org>
<434A2792.1070106@infinito.it>
<didaip$2me3$1@news.hub.org>
<dideic$1ppa$1@news.hub.org>
<20560.1128954447@sss.pgh.pa.us>
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).
One possibility is to add something like this immediately below the
chart in the page above:
---snip---
NOTE: SQL_ASCII _does not_ enforce a 7 bit restriction on insertions.
SQL_ASCII does not represent a positive claim that the database knows
all the characters to be 7 bit characters. It represents instead the
complete absence of any encoding knowledge. Inserting high-bit
characters into a database using the SQL_ASCII character set may have
unpredictable results.
---snip---
--
Andrew Sullivan | ajs@crankycanuck.ca
I remember when computers were frustrating because they *did* exactly what
you told them to. That actually seems sort of quaint now.
--J.D. Baldwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: character problem
In-Reply-To: <20051012212642.GA13571@phlogiston.dyndns.org>
References: <4349106C.6080206@infinito.it> <did562$epf$1@news.hub.org> <434A2792.1070106@infinito.it> <didaip$2me3$1@news.hub.org> <dideic$1ppa$1@news.hub.org> <20560.1128954447@sss.pgh.pa.us> <20051012212642.GA13571@phlogiston.dyndns.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox