From: Bryce Nesbitt <bryce2@obviously.com>
To: pgsql-sql@postgresql.org
Cc: Craig Ringer <craig@postnewspapers.com.au>
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Date: Tue, 03 Nov 2009 19:36:07 -0800
Message-ID: <4AF0F6A7.7070505@obviously.com> (raw)
In-Reply-To: <4AF0E70F.1030201@postnewspapers.com.au>
References: <4AF0D531.5080309@obviously.com>
<4AF0E70F.1030201@postnewspapers.com.au>
Craig Ringer wrote:
> In truth, that's how I'd expect it to happen. If I ask for the byte 0xfd
> in a string, I don't want the server to decide that I must've meant
> something else because I have a different client encoding. If I wanted
> encoding conversion, I wouldn't have written it in an escape form, I'd
> have written 'ý' not '\375'.
I've got a client encoding of LATIN1... so I'd expect to be able to
present any valid LATIN1 character, not care how the backend stored it,
then get the same character back from the database.
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bryce2@obviously.com, craig@postnewspapers.com.au
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
In-Reply-To: <4AF0F6A7.7070505@obviously.com>
* 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