Re: tsearch bug in 7.2.1? - Mailing list pgsql-hackers

Actually, looking at this again it's possible that tsearch sees 'a' as a
skip word and so doesn't allow a search on it.  This makes it _really_ hard
for me to parse and check user keywords - maybe a 'isvalidsyntax' sort of
function should be included?  Hmmm...maybe I could use the cast to
::mquery_txt to check it...but now I have to detect an ERROR condition and
deal with it appropriately...

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Christopher
> Kings-Lynne
> Sent: Thursday, 15 August 2002 1:43 PM
> To: Hackers
> Subject: [HACKERS] tsearch bug in 7.2.1?
>
>
> Hi,
>
> I noticed this behaviour:
>
> usa=# SELECT rr.id, rr.name, rr.description FROM recipe_recipes rr WHERE
> rr.ftiidx ## 's';
>  id  |               name               |
> description
> -----+----------------------------------+-------------------------
> ----------
> ------------------------------------------------
>  202 | Bird's Nest                      | An egg nestled in a crispy, hot
> bread roll.
>  293 | Reuben Triple S                  | Corn beef, swiss cheese and
> sauerkraut on pumpernickel.
>   30 | Hedgehogs                        | This is comfort food at it's
> yummiest.
>  130 | Hearty Apple & Cinnamon Porridge | A great way to warm you up on a
> winter's morning.
>   83 | Banana & Apple Compote           | Great way to finish a meal on a
> cool winter's day.
>  139 | Minestrone                       | Served with a crusty roll, this
> soup is a meal on it's own.
>   75 | Mango Sorbet                     | A mango-lover's delight.
>   19 | Chunky Vegetable Chowder         | Serve this soup with a
> crusty roll
> and it's a hearty meal on a cold winter's eve.
>   36 | Lemon Fish Rolls                 | A pleasant way to
> include fish in
> your family's diet.
> (9 rows)
>
> usa=# SELECT rr.id, rr.name, rr.description FROM recipe_recipes rr WHERE
> rr.ftiidx ## 's|a';
> ERROR:  Your query contained only stopword(s), ignored
> usa=# SELECT rr.id, rr.name, rr.description FROM recipe_recipes rr WHERE
> rr.ftiidx ## 's|x';
>  id  |               name               |
> description
> -----+----------------------------------+-------------------------
> ----------
> ------------------------------------------------
>  202 | Bird's Nest                      | An egg nestled in a crispy, hot
> bread roll.
>  293 | Reuben Triple S                  | Corn beef, swiss cheese and
> sauerkraut on pumpernickel.
>   30 | Hedgehogs                        | This is comfort food at it's
> yummiest.
>  130 | Hearty Apple & Cinnamon Porridge | A great way to warm you up on a
> winter's morning.
>   83 | Banana & Apple Compote           | Great way to finish a meal on a
> cool winter's day.
>  139 | Minestrone                       | Served with a crusty roll, this
> soup is a meal on it's own.
>   75 | Mango Sorbet                     | A mango-lover's delight.
>   19 | Chunky Vegetable Chowder         | Serve this soup with a
> crusty roll
> and it's a hearty meal on a cold winter's eve.
>   36 | Lemon Fish Rolls                 | A pleasant way to
> include fish in
> your family's diet.
> (9 rows)
> usa=# SELECT rr.id, rr.name, rr.description FROM recipe_recipes rr WHERE
> rr.ftiidx ## 'st|a';
> ERROR:  Your query contained only stopword(s), ignored
> usa=# SELECT rr.id, rr.name, rr.description FROM recipe_recipes rr WHERE
> rr.ftiidx ## 'st|ar';
>  id | name | description
> ----+------+-------------
> (0 rows)
>
> I don't see how that's correct?  Those ERRORs seem to be valid syntax to
> me...
>
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>