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:
[color=blue]
> I currently have a DB setup with ENCODING = UNICODE. Are all char, and
> varchars stored as UNICODE?[/color]

Yes.
[color=blue]
> 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?[/color]

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


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

> > Also, I get the general impression(from newsgroups, forums,[color=blue]
> etc...) that PG[color=green]
> > is rough around the edges when dealing with Unicode, is this[/color]
> the case, or[color=green]
> > just a bunch of noisy people?[/color]
>
> One particular problem is that there is poor (i.e., no) support for
> localized collation orders in Unicode databases.[/color]

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




---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster