Hi,
Since PostgreSQL is by default case sensitive, I would like to know if it is
possible to do a search or somehow set the column in a relation to be case
insensitive (on search at least).
I would however like to store it case sensitive so I can display it as it
was stored.
Ps. I am not interes
Richard, I was refereing to the plainto_tsquery
Oleg, I only need colasque if any of those columns can be null, which is not
the case here. Correct?
rule for partial indexes - you should use the same
> expression in query as you used in create index command.
>
> Oleg
> On Fri, 6 Feb 2009, James Dooley wrote:
>
> Oleg, but I am only interested in whether or not the syntax of my
>> search-query is correct.
>>
>> H
On Fri, Feb 6, 2009 at 4:01 PM, Richard Huxton wrote:
> James - don't repeat the whole of the previous message in your replies,
> trim it to the relevant part. The message is already archived on the list.
>
> James Dooley wrote:
> > Oleg, but I am only interested in wheth
car')
or should it be as Richard just mentioned
... AND to_tsvector(title || '' || description || '' || name) @@
plainto_tsquery('car')
or some other way ?
On Fri, Feb 6, 2009 at 3:30 PM, Richard Huxton wrote:
> James Dooley wrote:
> > Hi again,
&g
Hi again,
I have set my configuration as default and I have created a GIN index on
three columns, like this
create index textsearch_index on products using gin(strip( to_tsvector(
'my_config', title || '' || description || '' || name)))
Searching these columns the way I have
... AND (title || '
Hi,
How can I turn off the positioning since I won't be needing it.
SELECT to_tsvector('english','in the list of stop words');
to_tsvector
'list':3 'stop':5 'word':6
I don't need to store the positions as shown in the example because I rank
according to date
In
http://www.postgresql.org/docs/8.3/interactive/textsearch-dictionaries.html
it mention this feature for support on splitting compound words.
Adding the line
compoundwords controlles z
to the affix file returns an error
ERROR: wrong affix file format for flag
It's postgresql-8.3.5-2 (windows)
On Tue, Feb 3, 2009 at 4:37 PM, Tom Lane wrote:
> James Dooley writes:
> > and when building the Ispell dictionary I got the following error
>
> > ERROR: invalid byte sequence for encoding "UTF8": 0xe9640a
>
> What P
I downloaded the hunspell en_GB from
http://wiki.services.openoffice.org/wiki/Dictionaries#English_.28AU.2CCA.2CGB.2CNZ.2CUS.2CZA.29
and when building the Ispell dictionary I got the following error
ERROR: invalid byte sequence for encoding "UTF8": 0xe9640a
HINT: This error can also happen if
10 matches
Mail list logo