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

-----Urspr√ľngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Heikki 
Gesendet: Freitag, 15. September 2006 13:35
An: Martijn van Oosterhout
Cc: [EMAIL PROTECTED]; pgsql-hackers@postgresql.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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to