Re: Fixed length data types issue

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: stark(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fixed length data types issue
Date: 2006-09-15 11:34:42
Message-ID: 450A8FD2.4070407@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout wrote:
> I don't think making a special typlen value just for a type that can
> store a single UTF-8 character is smart. I just can't see enough use to
> make it worth it.
>

Assuming that we can set encoding per-column one day, I agree. If you
have a CHAR(1) field, you're going to store codes like 'A', 'B', 'C' or
'1', '2', '3' in it, and you don't need UTF-8 for that.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mario Weilguni 2006-09-15 11:38:54 Re: Fixed length data types issue
Previous Message Martijn van Oosterhout 2006-09-15 10:52:44 Re: Fixed length data types issue