Last modified: 2007-02-22 17:38:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8958 - wrong query parser for tsearch2 (pgsql)
wrong query parser for tsearch2 (pgsql)
Product: MediaWiki
Classification: Unclassified
Search (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: postgres
  Show dependency treegraph
Reported: 2007-02-12 14:41 UTC by Cédric
Modified: 2007-02-22 17:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

rewrite using tsearch2 valid operators (1.82 KB, patch)
2007-02-12 14:43 UTC, Cédric

Description Cédric 2007-02-12 14:41:38 UTC
it seems taht the query parser do the job for mysql not for pgsql :
operators in tsearch query are : () ! | & but + and - are used

I have patch include/SearchPostgres.php to rewrite using the above operators (I have made some tests, 
but not all ....).

Know issue : if you search only by the absence of a word there is strange behaviour (I think this is 
more mediawiki code than specific postgresql code)
Comment 1 Cédric 2007-02-12 14:43:18 UTC
Created attachment 3211 [details]
rewrite using tsearch2 valid operators

make more test than I did ....
Comment 2 Greg Sabino Mullane 2007-02-22 17:36:49 UTC
Thanks for the patch - applied in r20040
Added notes about the <. >, and ~ operators - don't know if there 
is an easy way for tsearch2 to implement them.

Note You need to log in before you can comment on or make changes to this bug.