Last modified: 2007-03-24 17:50: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 8838 - searching for floats without units doesn't work right
searching for floats without units doesn't work right
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Markus Krötzsch
http://ontoworld.org/index.php?title=...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-31 07:04 UTC by S Page
Modified: 2007-03-24 17:50 UTC (History)
1 user (show)

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


Attachments

Description S Page 2007-01-31 07:04:37 UTC
Searching for a value of an attribute of Type:Float without units doesn't return
pages with that value that do have units.

E.g. if attribute values are 42 (no value), 42 km, and 42 miles; then searching
for 42 only finds the first one.

SpecialSearchTriple's searchAttributes() always queries on unit, even if unit is
blank.  Maybe it should treat a blank unit as NULL unit so it doesn't search on it.

This may only be true for SearchTriple, but I think AskSpecial has issues also.

(If an attribute is of a type that does support unit conversions, then I believe
leaving off the unit triggers the default unit conversion.  I think that's
reasonable behavior.)
Comment 1 Markus Krötzsch 2007-03-24 17:50:12 UTC
Special:SearchTriple is about to be rewritten, so we have to wait which new
specials appear and which problems they have. In general, they are likely to
behave much like <ask> and its special, since all unit handling is now taken
care of by SMWDataValue which is passed on for searching a value -- the caller
no longer decides which untis are passed, but merely generates an SMWDataValue
which does this.

I think this closes this bug.

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


Navigation
Links