| From: | Mark Rotteveel <mark(at)lawinegevaar(dot)nl> |
|---|---|
| To: | <dbadmin(at)nqadmin(dot)com> |
| Cc: | <pgsql-jdbc(at)postgresql(dot)org>, John R Pierce <pierce(at)hogranch(dot)com> |
| Subject: | Re: Re: Fwd: Re: Re: Postgresql 9.4.4 - ERROR: invalid byte sequence for encoding "UTF8": 0x92 |
| Date: | 2015-08-09 09:49:45 |
| Message-ID: | 9e1a529b606da0d25b20e3031ad661f0@imap.procolix.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, 08 Aug 2015 17:34:15 -0500, Prasanth Reddy <dbadmin(at)nqadmin(dot)com>
wrote:
> 2. I am able to view the content in pgadmin, why would the server not
> complain when viewing from pgadmin. Not sure what the client encoding
would
> be when using pgadmin.
pgadmin probably doesn't apply any encoding, but uses the bytes as is.
> 3. Thought SQL_ASCII means the text is stored as ASCII format, may be I
am
> way off base on this. Is there a way to check the notes column for
invalid
> UTF8 characters and remove them?
0x92 is not a valid ASCII character, ASCII characters are in the range
0x00-0x7F. 0x92 is in the 'extended ascii range', but that is not really
defined, andvdepends on the actual encoding (the real character set), that
is why the conversion fails.
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prasanth Reddy | 2015-08-09 18:44:51 | Re: Fwd: Re: Re: Postgresql 9.4.4 - ERROR: invalid byte sequence for encoding "UTF8": 0x92 |
| Previous Message | Prasanth Reddy | 2015-08-08 22:34:15 | Re: Fwd: Re: Re: Postgresql 9.4.4 - ERROR: invalid byte sequence for encoding "UTF8": 0x92 |