On Thursday 26 June 2008 15:41, Michael Fuhr wrote:
> On Thu, Jun 26, 2008 at 03:31:01PM +0200, Albe Laurenz wrote:
> > Michael Fuhr wrote:
> > > Your input data seems to have a mix of encodings: sometimes you're
> > > getting pound signs in a non-UTF-8 encoding, but if characters like
> > > got i
On Thu, Jun 26, 2008 at 03:31:01PM +0200, Albe Laurenz wrote:
> Michael Fuhr wrote:
> > Your input data seems to have a mix of encodings: sometimes you're
> > getting pound signs in a non-UTF-8 encoding, but if characters like
> > got into the database when
> > client_encoding was set to UTF8 then
Michael Fuhr wrote:
> > > ProgrammingError Error Value: ERROR: character 0xe28099 of
> > > encoding "UTF8" has no equivalent in "LATIN1" select distinct
> > [...]
> >
> > This is UNICODE 0x2019, a "right single quotation mark".
> >
> > This is a "Windows character" - the only non-UNICODE codepage
On Tue, Jun 24, 2008 at 09:16:37AM +0200, Albe Laurenz wrote:
> Garry Saddington wrote:
> > ProgrammingError Error Value: ERROR: character 0xe28099 of
> > encoding "UTF8" has no equivalent in "LATIN1" select distinct
> [...]
>
> This is UNICODE 0x2019, a "right single quotation mark".
>
> This is
Garry Saddington wrote:
> I have the following error:
>
> Postgres 8.3 via psycopg 1.1.21 and zope 2.10.
>
> ProgrammingError Error Value: ERROR: character 0xe28099 of encoding "UTF8"
> has no equivalent in "LATIN1" select distinct
[...]
This is UNICODE 0x2019, a "right single quotation mark".
I have the following error:
Postgres 8.3 via psycopg 1.1.21 and zope 2.10.
ProgrammingError Error Value: ERROR: character 0xe28099 of encoding "UTF8" has
no equivalent in "LATIN1" select distinct teachers.teacherid,teachers.teacherid
as thisteacherid,teachers.initials,
reports.reporttext,report
