> You mean chr(0x85). This looks like Windows-1252 encoding. You need to
> recode this to UTF-8 if your database is set to UTF-8. In principle,
> that can be achieved like this:
>
> chr(0x85).decode('cp1252').encode('utf-8')You are absolutely correct on both accounts. The database is setup to be UTF-8. The application I am working with transfers data records from an old file system base database ( ISAM files), and the chr(0x85) is embedded in a string that is part of a field. The solution offered no doubt works great, but as I understand this, I would need to modify our utility encode each field and my perception would be that would be quite a performance hit. So I guess what I was hoping to find is some setting so that the pg client (libpq)client automatically does the encoding. Is this possible ? g. _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
