From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
---|---|
To: | Swaminathan Saikumar <swami(at)giveexam(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unicode comment on Postgres vs Sql Server |
Date: | 2008-03-02 20:44:24 |
Message-ID: | 47CB11A8.9000107@wildenhain.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Swaminathan Saikumar wrote:
> I am familiar with MS Sql Server & just started using Postgres.
> For storing Unicode, Sql Server uses nvarchar/char for unicode, and uses
> char/varchar for ASCII.
> Postgres has this encoding setting at the database level.
>
> I am using UTF8 Unicode for most of my data, but there is some data that
> I know for sure will be ASCII. However, this is also stored as UTF8,
> using up more space.
This is wrong - ASCII is a subset of UTF8 and therefore uses
exactly one byte for every ASCII char.
See http://en.wikipedia.org/wiki/UTF-8 for example.
>
> At first sight, it looks like the the more granular level design is
> better. Any comments? If you agree, does it make sense to add this as a
> new datatype to Postgres?
Which new datatype?
Regards
Tino
From | Date | Subject | |
---|---|---|---|
Next Message | Swaminathan Saikumar | 2008-03-02 20:54:43 | Re: Unicode comment on Postgres vs Sql Server |
Previous Message | Leif B. Kristensen | 2008-03-02 20:32:05 | Re: Unicode comment on Postgres vs Sql Server |