encoding advice requested

From: Rick Schumeyer <rschumeyer(at)ieee(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: encoding advice requested
Date: 2006-11-11 19:45:00
Message-ID: 4556283C.5020305@ieee.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

My database locale is en_US, and by default my databases are UTF8.

My application code allows the user to paste text into a box and submit
it to the database. Sometimes the pasted text contains non UTF8
characters, typically the "fancy" forms of quotes and apostrophes. The
database does not appreciate it when the application attempts to store
these characters.

What is the best option to deal with this problem?

a) I think I could re-create the database with a LATIN1 encoding. I'm
not real experienced with different encodings, are there any issues with
combining en_US and LATIN1?

b) I can issue a SET CLIENT_ENCODING TO 'LATIN1'; statement every time I
open a connection. A brief test indicates this will work.

c) I can figure out how to filter the text in the application
program...but this seems like wasted work considering I could use either
option A or B.

Opinions?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2006-11-11 20:26:33 Re: Why overlaps is not working
Previous Message Andrus 2006-11-11 19:43:25 Re: Why overlaps is not working