From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tsearch_core for inclusion |
Date: | 2007-03-16 16:16:15 |
Message-ID: | Pine.LNX.4.64.0703161909080.400@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 16 Mar 2007, Joshua D. Drake wrote:
>
>> One a related note - will to_tsvector and to_tsquery be renamed to
>> something like ft_parse_text() and ft_parse_query() if tsearch2 goes
>
> Furthering this... perhaps even:
>
> ft_search()
> ft_query()
ts_ means Text Search, I don't think ft_ (Full Text) is better.
Going further it should be fts_ (Full Text Search), but we have
many concerns about compatibility and stability of api, so I'd prefer
to stay with ts_.
The more important is what syntax we should accept for the final patch ?
Original proposed or modified version ?
On
http://mira.sai.msu.su/~megera/pgsql/ftsdoc/fts-syntax-compare.html
they are D.1.2 and D.1.3
As I understood Teodor's proposal about CREATE INDEX command is ok for all.
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2007-03-16 16:18:55 | Re: tsearch_core for inclusion |
Previous Message | Andrew Dunstan | 2007-03-16 15:24:40 | Re: tsearch_core for inclusion |