| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | Richard Emberson <emberson(at)phc(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: text vs varchar(n) |
| Date: | 2002-02-18 09:52:49 |
| Message-ID: | 200202180952.g1I9qnFP005662@www1.translationforge |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le Lundi 18 Février 2002 06:52, Richard Emberson a écrit :
> If ones sets up the db to be UNICODE, does that also apply to the 'text'
> type?
Yes, encoding is set at database creation (CREATE DATABASE foo WITH ENCODING
'Unicode') for all database. This applies to all tables and views. Unicode is
handled as fast as Latin1 with no real impact on performances.
When using a Unicode PostgreSQL database, you also need a Unicode backend
like Apache/PHP or Java. If your backend is Latin1, like VB6, PostgreSQL will
not be able to recode from Unicode to Latin1 transparently.
Please also note that some server-side functions do not support unicode yet.
Cheers,
Jean-Michel POURE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Fabiani | 2002-02-18 10:34:22 | Can postgres use the login password |
| Previous Message | Jean-Michel POURE | 2002-02-18 09:40:59 | Re: Database Performance? |