| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dan McFadyen" <danm(at)cryptocard(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Odd query behavior |
| Date: | 2010-03-15 17:14:21 |
| Message-ID: | 20344.1268673261@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Dan McFadyen" <danm(at)cryptocard(dot)com> writes:
> Now, the interesting part is for all I can tell, there are no special
> characters in the field. Unless the latest version of Pgadmin (1.10.1 or
> 1.10.2) hides this from the UI, either that or it's some character that
> renders into a similar glyph as ASCII.
> Is there any way to force hex/binary in a SQL statement?
Huh. Try pg_dump'ing the table and then searching the file for any
bytes with high bit set.
It's possible that Finnish locale sorts some of the plain-ASCII
characters differently than C locale would, but I don't know of
a reason for that to break anything.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eduardo Palafox | 2010-03-15 17:18:56 | Please delete my email |
| Previous Message | Dan McFadyen | 2010-03-15 17:01:53 | Re: Odd query behavior |