MultiByte Columns?
I currently have a DB setup with ENCODING = UNICODE. Are all char, and
varchars stored as UNICODE? I predominantly work in a SQL Server
environment, and there we have varchar for regular ASCII, and nvarchar for
Unicode, so the extra space is used only when necessary. I just wanted to
find out if PG takes care of this behind the scenes, or if everything for
the DB is stored as multi-byte.
Also, I get the general impression(from newsgroups, forums, etc...) that PG
is rough around the edges when dealing with Unicode, is this the case, or
just a bunch of noisy people?
Thanks,
Steve
Steve - DND writes:
I currently have a DB setup with ENCODING = UNICODE. Are all char, and
varchars stored as UNICODE?
Yes.
Also, I get the general impression(from newsgroups, forums, etc...) that PG
is rough around the edges when dealing with Unicode, is this the case, or
just a bunch of noisy people?
One particular problem is that there is poor (i.e., no) support for
localized collation orders in Unicode databases.
--
Peter Eisentraut peter_e@gmx.net
Also, I get the general impression(from newsgroups, forums,
etc...) that PG
is rough around the edges when dealing with Unicode, is this
the case, or
just a bunch of noisy people?
One particular problem is that there is poor (i.e., no) support for
localized collation orders in Unicode databases.
Do you know if there is there planning to make PG more Unicode friendly in
the future? If so, any idea around what version they're expecting it to be?
Thanks,
Steve