Re: Fixed length data types issue

What about the "char" type? Isn't it designed for that? Or will this type disappear in future releases?

-----Ursprüngliche Nachricht-----
Von: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-owner(at)postgresql(dot)org] Im Auftrag von Heikki Linnakangas
Gesendet: Freitag, 15. September 2006 13:35
An: Martijn van Oosterhout
Cc: stark(at)enterprisedb(dot)com; pgsql-hackers(at)postgresql(dot)org
Betreff: Re: [HACKERS] Fixed length data types issue

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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend