From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
---|---|
To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "Tom Lane *EXTERN*" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bad Data back Door |
Date: | 2012-10-08 07:30:49 |
Message-ID: | 43FA5AD0-F823-4906-974E-C37022E6B240@justatheory.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Oct 8, 2012, at 12:25 AM, "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
> As the author I agree that this is a bug in oracle_fdw.
Thanks. Should I file a report somewhere?
> This was caused by ignorance on my part: I had assumed that the
> type input functions would perform the necessary checks, but it
> seems like that is not the case. I'll look into it.
Thank you!
> Oracle does not care much about correct encoding.
> If client character set and database character set are the same,
> Oracle does not bother to check the data. This is probably how
> WINDOWS-1252 characters slipped into the UTF-8 database in question.
> I consider this a bug in Oracle, but never reported it, because
> I don't have much hope that Oracle would see it as a problem
> given their habitually sloppy handling of encoding issues.
Yeah, same here. I've been looking into write a function to try to fix poorly-encoded data, though, but haven't got far, because CONVERT() does not indicate failure. If you have any insight on this, I'd appreciate your thoughts on this Stack Overflow question:
http://stackoverflow.com/q/12717363/79202
Thanks,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Tachoires | 2012-10-08 07:49:27 | Re: Improving psql \ds |
Previous Message | Albe Laurenz | 2012-10-08 07:25:52 | Re: Bad Data back Door |