From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)de> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3964: Parsing error in Stack Builder with LATIN1 client encoding |
Date: | 2008-02-15 10:47:41 |
Message-ID: | 937d27e10802150247m177f7786pb8823c80ede4d57c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Feb 15, 2008 at 9:41 AM, Jan-Peter Seifert
<Jan-Peter(dot)Seifert(at)gmx(dot)de> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3964
> Logged by: Jan-Peter Seifert
> Email address: Jan-Peter(dot)Seifert(at)gmx(dot)de
> PostgreSQL version: 8.3.0
> Operating system: Windows xp sp2 German
> Description: Parsing error in Stack Builder with LATIN1 client
> encoding
> Details:
>
> When choosing LATIN1 instead of the default CP1252 for the client encoding I
> get this error in PostgreSQL & EnterpriseDB Stack Builder:
>
> 13:42:54: Fehler beim Lesen des XML: 'syntax error' in Zeile 1
> 13:42:54: Konnte die Anwendungsliste nicht parsen:
> http://www.postgresql.org/applications.xml
>
> It doesn't matter whether the server encoding is LATIN1 or not.
What exactly are you doing? Stackbuilder never talks to the database
server, and has no encoding options at all.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2008-02-15 12:12:39 | Re: BUG #3961: ecpg lacks SQLSTATE macro definition |
Previous Message | Jan-Peter Seifert | 2008-02-15 09:41:13 | BUG #3964: Parsing error in Stack Builder with LATIN1 client encoding |