| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, andrew(at)dunslane(dot)net, laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-11 04:04:13 |
| Message-ID: | 1189483453.5924.50.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Tue, 2007-09-11 at 11:53 +0900, Tatsuo Ishii wrote:
> > Isn't the collation a locale issue, not an encoding issue? Is there a
> > ja_JP.UTF-8 that defines the proper order?
>
> I don't think it helps. The point is, he needs different language's
> collation, while PostgreSQL allows only one collation(locale) per
> database cluster.
My thought was: if we had some function that treated a string as a
different locale, it might solve the problem without violating the
database encoding.
Converting to a different encoding, and producing text result, is the
source of the problem.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2007-09-11 05:06:34 | Testing 8.3 LDC vs. 8.2.4 with aggressive BGW |
| Previous Message | Tom Lane | 2007-09-11 04:01:36 | What is happening on buildfarm member dugong? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-09-11 04:42:38 | Re: HOT patch - version 15 |
| Previous Message | Pavan Deolasee | 2007-09-11 03:51:49 | Re: HOT patch - version 15 |