Last modified: 2011-03-13 18:05:10 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 13150 - Modified AskQueryOutput when using OR Query
Modified AskQueryOutput when using OR Query
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-25 12:30 UTC by DaSch
Modified: 2011-03-13 18:05 UTC (History)
0 users

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


Attachments

Description DaSch 2008-02-25 12:30:43 UTC
<ask format="ul">
[[Property1::Value1]]||[[Property2::Value1]]
</ask>

When using such a query there is only a list of pages given.

I think the list should contain the Property that is true. The list might look like this.

*Page1, (Property1)
*Page2, (Property2)
*Page3, (Property2)
*Page4, (Property1)
*Page5, (Property1,Property2)
*Page6, (Property2)
*Page7, (Property1)
Comment 1 DaSch 2008-02-25 14:16:12 UTC
The same thing could be useful for
<ask format="ul">
[[Property3::Value1]]
</ask>
When Property1 and Property2 are Subpropreties of Property3
Comment 2 Markus Krötzsch 2009-08-02 11:49:30 UTC
This sounds like a useful feature but it is hard to implement in practice, since it does not fit into the uniform result format that we use. Also, the need for tracking information about why a certain result is shown is making query answering more difficult. Doing this in SMW would lead to a decrease in performance. It should also be noted that this is not a feature that is common to many query languages: even SPARQL and SQL (which are more powerful than SMW' ask) do not have such a facility.

Based on these considerations, I reject this feature request. If there is strong interest in having this, then I would consider submitted code for inclusion in SMW, as long as it does not lead to significant performance reductions.

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


Navigation
Links