pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ivo Rossacher <rossacher@bluewin.ch>
To: pgsql-admin@postgresql.org
Subject: Re: encoding???
Date: Wed, 27 Feb 2008 00:53:24 +0100
Message-ID: <200802270053.24669.rossacher@bluewin.ch> (raw)
In-Reply-To: <5AE10E7F-7AAD-4717-83E8-CD49BAE49F6F@indiana.edu>
References: <5AE10E7F-7AAD-4717-83E8-CD49BAE49F6F@indiana.edu>

SQL_ASCII is not really an encoding, it is more the lack of any encoding 
support from the server. With this setting the encoding is fully the 
responsibility of the client application.
This is very comfortable for special cases but for most regular cases it is 
only asking for troubles.
Therfore for most cases UTF8 should be the prefered encoding on the server 
side. The client encoding only tells the server how to convert the data from 
and to the client. How to set this depends on the capabilities of the client.

In the manual in chapter 22.2 Character Set Support you can get more details 
and all from the server supported conversions.

Best regards
Ivo
 
Am Dienstag, 26. Februar 2008 20.41:45 schrieb Carol Walter:
> Greetings...
>
> I'm really confused about something.  I hope you'll help.  I have a
> client who wants to use Asian Character data.  The database he wants
> to use is set to SQL_ASCII, the default.  I thought there might be an
> ALTER DATABASE command that would change this, but I've been through
> the documentation and it says that encoding is done at the client
> level and is changed with a set statement.  I assumed that would be
> like setting the search path so I tried it and I was able to set the
> encoding for my session to UTF8.  I guess my question is how does
> this work, where the database is set to use one encoding sequence and
> it is set for the client session to something else.
>
> Carol Walter
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster





view thread (3+ messages)

Message-ID: <200802270053.24669.rossacher@bluewin.ch>
Permalink:  ../200802270053.24669.rossacher@bluewin.ch/
Also on:    postgresql.org/message-id/200802270053.24669.rossacher@bluewin.ch

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: rossacher@bluewin.ch
  Subject: Re: encoding???
  In-Reply-To: <200802270053.24669.rossacher@bluewin.ch>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox