Re: Fixed length data types issue - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Fixed length data types issue
Date
Msg-id 20060908103946.GB5479@svana.org
Whole thread Raw
In response to Re: Fixed length data types issue  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Fixed length data types issue
List pgsql-hackers
On Fri, Sep 08, 2006 at 05:54:01AM -0400, Andrew Dunstan wrote:
> >The encoding is set per-database. Even if you need UTF-8 to encode
> >user-supplied strings, there can still be many small ASCII fields in
> >the database. Country code, currency code etc.
>
> ISTM we should revisit this when we get per-column encoding.

I think that if SQL COLLATE gets in we'll get this almost for free.
Collation and charset are both properties of strings. Once you've got a
mechanism to know the collation of a string, you just attach the
charset to the same place. The only difference is that changing charsets
requires recoding, wheres changing collation does not.

I think it'd just become a special case of the Relabel node.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Fixed length data types issue
Next
From: Heikki Linnakangas
Date:
Subject: Re: Fixed length data types issue