| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Dan Hrabarchuk" <dan(at)geotivity(dot)net> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #3944: Unable to create a database using SQL_ASCII encoding |
| Date: | 2008-02-08 21:54:51 |
| Message-ID: | 47ACCFAB.7090105@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dan Hrabarchuk wrote:
> How do I use standard ASCII? My legacy app in not compatible with unicode.
You can use the C-locale, see the user manual, section "22.1 Locale
Support" for more information:
http://www.postgresql.org/docs/8.3/interactive/locale.html
However, you don't have to use SQL_ASCII in the server, even if you have
a legacy app that doesn't grok unicode. The encoding used to communicate
with the client can be set on a connection-by-connection basis with the
client_encoding setting, and it doesn't have to match the server encoding.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Holger Klawitter | 2008-02-08 22:20:18 | BUG #3945: unexpected ON INSERT rule behaviour |
| Previous Message | Tom Lane | 2008-02-08 21:44:24 | Re: BUG #3944: Unable to create a database using SQL_ASCII encoding |