Re: Mixed client_encoding database: what to do with..

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Mixed client_encoding database: what to do with..
Date: 2011-01-11 21:40:57
Message-ID: AANLkTim4On6S_Y-QuBGvA94vtVtYc635twbhkZ_37Ge=@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jan 11, 2011 at 3:23 AM, J. Hondius <jhondius(at)rem(dot)nl> wrote:
> -Should i filter out all non win1252 charachters at the new java app and
> substitute them? (not so nice, i'd like to have the chars in the db)
>

If one of your client's cannot handle the data stored in the DB, then
you should not store that data in the DB. So I think this is your best
option. This way you are in control of how those characters are
mapped.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tomas Vondra 2011-01-11 21:41:08 Re: database is growing... 1GB per day basis
Previous Message M Sabin 2011-01-11 21:03:28 Postgres in FIPS