| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: tsearch in core patch, for inclusion |
| Date: | 2007-01-24 21:21:43 |
| Message-ID: | 200701242221.45150.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stefan Kaltenbrunner wrote:
> I think one can find arguments for both variants - one of the
> question might even be how other databases are doing that and if the
> proposed syntax is resembling one of those or not.
The closest I could find is Oracle Text, the full-text search for
Oracle. Browsing the documentation I see things like
exec ctx_ddl.create_preference('myjlexer','japanese_lexer');
exec ctx_ddl.add_stopword('globallist','the','French');
which look pretty similar to what a procedure-based interface to
tsearch2 could look like.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-01-24 21:27:10 | Re: tsearch in core patch, for inclusion |
| Previous Message | Joshua D. Drake | 2007-01-24 21:15:12 | Re: tsearch in core patch, for inclusion |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-01-24 21:27:10 | Re: tsearch in core patch, for inclusion |
| Previous Message | Joshua D. Drake | 2007-01-24 21:15:12 | Re: tsearch in core patch, for inclusion |