Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3944: Unable to create a database using SQL_ASCII encoding
- 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: Fri, 08 Feb 2008 21:54:51 +0000
- Message-id: <47ACCFAB(dot)7090105(at)enterprisedb(dot)com>
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.htmlHowever, 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
- References:
- BUG #3944: Unable to create a database using SQL_ASCII encoding
- From: Dan Hrabarchuk
- BUG #3944: Unable to create a database using SQL_ASCII encoding
- Prev by Date: Re: BUG #3944: Unable to create a database using SQL_ASCII encoding
- Next by Date: BUG #3945: unexpected ON INSERT rule behaviour
- Previous by thread: Re: BUG #3944: Unable to create a database using SQL_ASCII encoding
- Next by thread: BUG #3945: unexpected ON INSERT rule behaviour
- Indexes: