| From: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | markus(at)bluegap(dot)ch, teodor(at)sigaev(dot)ru, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsearch in core patch, for inclusion |
| Date: | 2007-02-22 17:55:55 |
| Message-ID: | BAY20-F21A2F83830E0512DF9CF66F98F0@phx.gbl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>I am not talking about stored procedures. I am talking about a very
>ugly, counter intuitive syntax above.
>
>Initializing full text should be as simple as:
>
>CREATE INDEX foo USING FULLTEXT(bar);
>
>(or something similar)
>
>Or:
>
>CREATE TABLE foo (id serial, names text FULLTEXT);
>
>Anything more complicated is a waste of cycles.
>
>Joshua D. Drake
I agree. Question: what about multilanguage fulltext.
CREATE INDEX foo USING FULLTEXT(bar) [ WITH czech_dictionary ];
CREATE TABLE foo (id serial, names text FULLTEXT [ (czech_dictionary,
english_dictionary) ] );
all others can we do via SP.
Pavel Stehule
_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-02-22 18:00:00 | Re: SCMS question |
| Previous Message | Andrew Dunstan | 2007-02-22 17:53:07 | Re: SCMS question |