From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Fabio Serra" <faser(at)faser(dot)net>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Error Message |
Date: | 2003-07-03 20:43:13 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B83AF161@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Fabio Serra [mailto:faser(at)faser(dot)net]
> Sent: 03 July 2003 11:34
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] Error Message
>
>
> Description: ERROR: Invalid UNICODE character sequence
> found (0xe02073)
> Number: -2147467259
> Routine: pgAdmin II:frmSQLInput.cmdExecute_Click
>
> ************************************************************
>
> Insert your comment:
> The error occured while I was creating a database from an SQL
> script. The
> same script works well with Database ASCII Encoded. The error
> occured near
> these lines:
Hi,
The error itself is coming from PostgreSQL rather than pgAdmin. It's
possible that pgAdmin is incorrectly sending a Unicode character (it
doesn't support Unicode) which is tripping it up. Whatever the case,
there is unlikely to be anything we can do in pgAdmin to fix the
problem.
I can suggest a couple of things though - firstly, you might try a
snapshot release of pgAdmin III from http://www.pgadmin.org/snapshots/.
pgAdmin III has a much better SQL tool with full Unicode support.
Alternatvely, you might try running your script in psql.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-07-03 20:53:22 | Re: [pgadmin-support] [GENERAL] pgAdmin III - Call for Translators |
Previous Message | Andreas Pflug | 2003-07-03 20:40:43 | Re: Windows 2000 Server and PostgreSQL |