Last modified: 2013-11-17 19:23:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59151, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57151 - Allow matching #ask strings with a length > 72
Allow matching #ask strings with a length > 72
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-17 19:15 UTC by d3mon
Modified: 2013-11-17 19:23 UTC (History)
4 users (show)

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


Attachments

Description d3mon 2013-11-17 19:15:29 UTC
When performing #ask queries like the one below, searched text is not matched on the o_blob field:

{{#ask: [[Property::~*Some text*]]
| ?Something
| format=table
}}

Properties that go over the 72 character length listed in
SMW_DIHandler_String.php are split, so the end of the text gets changed in o_hash, and the full text is registered in o_blob.  The Problem is, #ask only seems to be matching on text in the o_hash column.   If I change the 72
character limit to something like 200 characters, the ask function matches
just fine.  I figure there's probably a better solution, or fix, than that
though?  If not, then would it hurt performance changing it to a
varchar(400) with 400 character limit on o_hash, or is it just a disk space
thing? I have a property which consists of a long string of keywords, and need the ability to match on any part of that string. Thanks!

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


Navigation
Links