On Tue, 21 Oct 2008 10:29:52 +0200
Ivan Sergio Borgonovo [EMAIL PROTECTED] wrote:
I came across this:
http://grokbase.com/topic/2007/08/07/general-tsearch2-plainto-tsquery-with-or/r92nI5l_k9S4iKcWdCxKs05yFQk
And I find it is strictly related to my needs.
Working around ts_parse I could get an
On Tue, 21 Oct 2008 13:20:12 +0200
Ivan Sergio Borgonovo [EMAIL PROTECTED] wrote:
On Tue, 21 Oct 2008 10:29:52 +0200
Ivan Sergio Borgonovo [EMAIL PROTECTED] wrote:
I came across this:
http://grokbase.com/topic/2007/08/07/general-tsearch2-plainto-tsquery-with-or/r92nI5l_k9S4iKcWdCxKs05yFQk
Ivan Sergio Borgonovo [EMAIL PROTECTED] writes:
It would still be nice to be able to directly work with tsvector
and tsquery so people could exploit the parser, lexer etc... and
recycle the config.
I'd thinking something in the line of
for lex in select * from to_tsvector('jsjdjd fdsds')
On Tue, 21 Oct 2008 10:36:20 -0400
Tom Lane [EMAIL PROTECTED] wrote:
Ivan Sergio Borgonovo [EMAIL PROTECTED] writes:
It would still be nice to be able to directly work with tsvector
and tsquery so people could exploit the parser, lexer etc... and
recycle the config.
I'd thinking
Ivan Sergio Borgonovo [EMAIL PROTECTED] writes:
I missed it. Thanks. Nearly perfect. Now I've to understand what a
{} is.
An array with a null element? an empty array? an array containing ''?
Hmm ... it appears that ts_lexize is returning a one-dimensional array of
no elements, whereas
