| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Latin vs non-Latin words in text search parsing |
| Date: | 2007-10-23 14:52:19 |
| Message-ID: | 7856AD6B-702B-4E39-9D97-54A06B46899C@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 23, 2007, at 10:42 , Tom Lane wrote:
> apart_hword Part of hyphenated word, all ASCII letters
> part_hword Part of hyphenated word, all letters
> numpart_hword Part of hyphenated word, mixed letters and digits
Is there a rationale for using these instead of hword_apart,
hword_part and hword_numpart? I find the latter to be more readable
as variable names. Or was your thought to be able to identify the
content from the first part of the variable name?
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-23 15:10:39 | Re: ts_rewrite aggregate API seems mighty ugly |
| Previous Message | Tom Lane | 2007-10-23 14:49:18 | Re: Latin vs non-Latin words in text search parsing |