[storm] Latin-1 Character Set

[James Henstridge]

[CC'ing the mailing list, since you dropped it in your reply]

On Wed, Oct 29, 2008 at 6:37 PM, kevin gill <kevin at movieextras.ie> wrote:
>> PostgreSQL should reencode input/output between the database encoding
>> and client encoding for text/character fields.
>>
>>     http://www.postgresql.org/docs/8.3/static/multibyte.html
>>
>> Storm sets the client encoding to UTF-8, which should work with any
>> database encoding (of course, some unicode strings passed to the
>> database may give errors if they can't be represented, but that is
>> what you'd expect.  Is this not happening for you?
>
> This is an old database which is connected to a Zope 2 site. The database
> is SQL_ASCII, and the Zope 2 system binds to it using latin-1 (PyscopgDA
> etc). The result is that there is data on the database encoded in latin-1
> but PostgreSQL has no rules for handling it.

That does sound like a problem.  I don't suppose you'd have the
opportunity to dump and restore your database with a correct encoding?
 The page I referenced above strongly recommends against use of that
encoding.

James.