| From: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
|---|---|
| To: | "Matthias Urlichs" <smurf(at)noris(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, =?iso-8859-1?Q?Moucha_V=E1clav_=3CMouchaV=40radiomobil=2Ecz=3E?=(at)noris(dot)de, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [BUGS] Re: Sigh, LIKE indexing is *still* broken in foreign locales |
| Date: | 2000-06-08 07:57:06 |
| Message-ID: | 3301.960451026@nemeton.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, 8 Jun 2000 08:53:25 +0200 "Matthias Urlichs" wrote:
> To find the position in the index where it should start scanning.
Hmm. That I guess is faster than locating the prefix given to LIKE in
the index and scanning back as well as forward.
> Personally, I am in the "store everything on the server in Unicode"
> camp. Let the parser convert everything to Unicode on the way in,
> and vice versa.
That would help the charater set problem, although there are people
that argue that Unicode is not acceptable for all languages. (I only
note this; I don't have an opinion.)
I don't see that using Unicode helps very much with collation though
-- surely collation must still be locale specific, and the problems
with two-pass algorithms, and two-to-one and one-to-two mappings are
unchanged?
Regards,
Giles
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Kelly | 2000-06-08 09:33:46 | "IpcMemoryCreate: shmget failed" on 2.0.38 (was Re: Bug?) |
| Previous Message | Matthias Urlichs | 2000-06-08 06:53:25 | Re: [HACKERS] Sigh, LIKE indexing is *still* broken in foreign locales |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-06-08 08:48:34 | AW: Look at heap_beginscan() |
| Previous Message | Magnus Hagander | 2000-06-08 07:47:02 | RE: day of week |