Johann Spies writes:
> On Thu, Jul 26, 2012 at 04:19:02PM +0800, Craig Ringer wrote:
>> You'll need to store language information alongside each text value
>> if you want to do anything more sophisticated.
> I was afraid that that will be the case :)
I'm not sure that there's anything horribly
On Thu, Jul 26, 2012 at 04:19:02PM +0800, Craig Ringer wrote:
> You'll need to store language information alongside each text value
> if you want to do anything more sophisticated.
I was afraid that that will be the case :)
I will have to update more than 32 entries which currently have
inc
On 07/26/2012 02:14 PM, Johann Spies wrote:
Hallo Tom,
I believe the problem is that the one-argument form of to_tsquery() uses
the default TS configuration, which you have probably not got set to
"simple". For me, the default TS configuration is "english", which will
stem "polity" as "politi"
Hallo Tom,
> I believe the problem is that the one-argument form of to_tsquery() uses
> the default TS configuration, which you have probably not got set to
> "simple". For me, the default TS configuration is "english", which will
> stem "polity" as "politi":
>
> regression=# select to_tsquery('
Johann Spies writes:
> I am beginning to use the full text search facilities in Postgresql
> (9.0) and find the result of this query a bit strange:
> query:
> SELECT ts_headline('simple',title, to_tsquery('kerkreg|(church & polity)'))
> from akb_articles A
> where A.tsv@@ 'kerkreg|(church & pol
I am beginning to use the full text search facilities in Postgresql
(9.0) and find the result of this query a bit strange:
query:
SELECT ts_headline('simple',title, to_tsquery('kerkreg|(church & polity)'))
from akb_articles A
where A.tsv@@ 'kerkreg|(church & polity)'
Result
"Kerkvereniging en
