Last modified: 2013-04-02 02:10:06 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 T30729, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28729 - The ! (not) Comparator doesn't work for many-valued properties
The ! (not) Comparator doesn't work for many-valued properties
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-27 22:44 UTC by tarkis13
Modified: 2013-04-02 02:10 UTC (History)
3 users (show)

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


Attachments

Description tarkis13 2011-04-27 22:44:19 UTC
Performing a query for pages that do not have a particular value, as in [[Type::!A]], returns pages with the excluded value so long as the page has other values specified for the relevant property.

An example can be seen in the SMW sandbox at http://sandbox.semantic-mediawiki.org/wiki/PageABTest

In that example, PageA has Type::A, while PageAB has Type::A and Type::B. The second and third queries ask for pages with Type::!A, which should exclude both pages, but only excludes PageA. PageAB is included in the results despite being exempted by the query. Other pages listed in second and third queries appear to be artifacts and are not relevant to the issue.

Even if this behavior is desired, a method of excluding pages where any member of a set of properties met the exclusion criteria would be helpful.
Comment 1 Jeroen De Dauw 2011-04-28 17:11:23 UTC
I had a quick look at this, but don't see how to nicely fix the query to not fail for this. Markus, can you take care of this one?
Comment 2 MWJames 2012-11-07 09:16:34 UTC
If this isn't fixed yet, it will not be fixed with SMW 1.8 but it should be made available in SMW 1.9 therefore I had this to the tracking ticket bug 41842.
Comment 3 Jeroen De Dauw 2013-01-10 15:45:45 UTC
James, are you planning to implement this? If so, fantastic. If not, we probably should not list it as something we'll do for 1.9.
Comment 4 Jeroen De Dauw 2013-04-02 02:10:06 UTC
Removing as blocker for 1.9

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


Navigation
Links