Re: 7.0.3 dumps aren't accessible via JDBC in 7.1 - Mailing list pgsql-bugs

From Peter T Mount
Subject Re: 7.0.3 dumps aren't accessible via JDBC in 7.1
Date
Msg-id 987765156.3ae019a42f1fa@webmail.retep.org.uk
Whole thread Raw
In response to 7.0.3 dumps aren't accessible via JDBC in 7.1  (pgsql-bugs@postgresql.org)
Responses RE: 7.0.3 dumps aren't accessible via JDBC in 7.1
List pgsql-bugs
Quoting pgsql-bugs@postgresql.org:

> Rainer Mager (rmager@vgkk.com) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> 7.0.3 dumps aren't accessible via JDBC in 7.1

I'd say this is not JDBC as JDBC doesn't deal with dumps, but...

> Long Description
> If the character '\255' exists in a 7.0.3 dump then JDBC barfs on
> reading this character in 7.1. Apparently this character is a dash
> character in unicode (not UTF-8), 0x00ad. The problem is that it is
> getting dumped (and restored) as a single byte and when JDBC reads it as
> 0xad it expects another byte after it (as according to the UTF-8 spec,
> anything over 0x7f must have another byte).

Hmmm, this sounds like either a backend issue, or something is misconfigured.
Have you got unicode support enabled in the backend?

Peter

--
Peter Mount peter@retep.org.uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/

pgsql-bugs by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: Re: position('' in '') returns 1 instead of 0
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Date Representation Bug. Timezone and update on an already posted as #208 reportbug