Dipsacus_fullonum updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T317941
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Dipsacus_fullonum
Cc: Aklapper, Dipsacus_fullonum, Astuthiodit_1, AWesterinen, karapayneWMDE
Dipsacus_fullonum updated the task description.
TASK DETAIL
https://phabricator.wikimedia.org/T317941
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Dipsacus_fullonum
Cc: Aklapper, Dipsacus_fullonum, Astuthiodit_1, AWesterinen, karapayneWMDE
Dipsacus_fullonum created this task.
Dipsacus_fullonum added a project: Wikidata-Query-Service.
Restricted Application added a subscriber: Aklapper.
TASK DESCRIPTION
**Steps to replicate the issue** (include links if applicable):
These two queries show the problem:
SELECT * WHERE
Dipsacus_fullonum added a comment.
It seems this feature is still undocumented (discussed in
https://www.wikidata.org/wiki/Wikidata_talk:SPARQL_query_service#title:). after
5 months In my opinion it is a waste of developer time to develop something,
and then don't make sure it is docum
Dipsacus_fullonum added a comment.
https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Full_statements
clearly states: //"There is no guaranteed format or meaning to the statement
id."// So why change an ID that should be stable when no specific format is
guarante
Dipsacus_fullonum added a comment.
Well, it seems that the requested feature already is here, but is
undocumented:
bd:serviceParam wikibase:limitContinuations "0".
Once the solution to T255753 <https://phabricator.wikimedia.org/T255753> is
implemented, it will
Dipsacus_fullonum added a comment.
https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual/MWAPI#Pagination
says:
> bd:serviceParam wikibase:limit "once" .
>
> This makes the service to stop after the first API call and not
Dipsacus_fullonum created this task.
Dipsacus_fullonum added a project: Wikidata-Query-Service.
Restricted Application added a subscriber: Aklapper.
Restricted Application added a project: Wikidata.
TASK DESCRIPTION
Feature request: When using MWAPI calls from Wikikdata Query Service, it
would
Dipsacus_fullonum created this task.
Dipsacus_fullonum added a project: Wikidata-Query-Service.
Restricted Application added a subscriber: Aklapper.
Restricted Application added a project: Wikidata.
TASK DESCRIPTION
Steps to Reproduce:
---
Example 1: Run this query
Dipsacus_fullonum added a comment.
@Lucas_Werkmeister_WMDE: Thank you for the explanation.
TASK DETAIL
https://phabricator.wikimedia.org/T253771
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Dipsacus_fullonum
Cc: Lucas_Werkmeister_WMDE
Dipsacus_fullonum created this task.
Dipsacus_fullonum added a project: Wikidata-Query-Service.
Restricted Application added a subscriber: Aklapper.
Restricted Application added a project: Wikidata.
TASK DESCRIPTION
This query:
# Query birthdate of Vespasian
SELECT ?date ?precision
Dipsacus_fullonum added a comment.
When I make an API call with action=query and generator=wblistentityusage,
like
https://en.wikipedia.org/w/api.php?action=query&generator=wblistentityusage&gwbeuentities=Q42
I get an RuntimeException:
{
"error": {
Dipsacus_fullonum added a comment.
Many queries use the optimizer hint `hint:Prior hint:rangeSafe true. ` when
e.g. comparing date or number values with constants in a filter as suggested at
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/query_optimization
Dipsacus_fullonum added a comment.
In T244341#6062871 <https://phabricator.wikimedia.org/T244341#6062871>,
@dcausse wrote:
> What we will implement internally for the isSomeValue function won't be
doing exactly `STRSTARTS( STR(?o), 'http://www.wikidata.org/prop/someva
Dipsacus_fullonum added a comment.
Yes, `isLiteral` should still work for properties where the real values are
literals. Without knowing the internal workings of Blazegraph I would guess
that it is more efficient than `STRSTARTS( STR(?o),
'http://www.wikidata.org/prop/some
Dipsacus_fullonum added a comment.
Here is an example where `isLiteral`is used that a value isn't somevalue:
https://stackoverflow.com/questions/53102725/make-filtering-people-by-birthyear-and-deathyear-criteria-more-performative-in-s
TASK DETAIL
https://phabricator.wikimedia.org/T2
Dipsacus_fullonum added a comment.
You should be aware that also the functions `isIRI` or `isLiteral` (depending
on property type) and `datatype` can be used and probably **is** used to test
if a value is somevalue or a real value.
TASK DETAIL
https://phabricator.wikimedia.org/T244341
Dipsacus_fullonum added a comment.
Fair enough, but the StackOverflowError seems to be a Blazegraph error, so
did anyone report the issue upstream? They have a Jira issue board at
https://jira.blazegraph.com/secure/Dashboard.jspa but I don't see anything
about this StackOverflowError.
Dipsacus_fullonum added a comment.
Why don't you close this as invalid and ask people to make correct SPARQL
code?
The SPARQL 1.1 specification clearly says in section "18.2.1 Variable Scope":
"The variable v must not be in-scope at the point of the (expr AS v) form.
Dipsacus_fullonum added a comment.
Also wikibase:quantityUnit is affected by this - unless the strange results
of this query is caused by something else:
SELECT ?item ?itemLabel ?amount ?unit ?unitLabel
WHERE
{
VALUES ?item { wd:Q20414458 }
?item p:P2048/psv:P2048
Dipsacus_fullonum added a comment.
Not a bug. Use of the Label service in automatic mode for unbound variables
in "GROUP BY" isn't mentioned as supported in the user manual
(https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Label_service)
so cannot be expected
Dipsacus_fullonum added a comment.
This seems to be the same or similar to T220829
<https://phabricator.wikimedia.org/T220829> (Wikidata edit (rollback) not
propagated to Wikipedia after 10 days)
TASK DETAIL
https://phabricator.wikimedia.org/T207651
EMAIL PREFERENCES
Dipsacus_fullonum added a comment.
I found the same problem at huwiki at the page
https://hu.wikipedia.org/wiki/Geert_Wilders by looking at the global file usage
for
the wrong image at https://commons.wikimedia.org/wiki/File:MarkRutte.jpg.
Again when logged in at huwíki I saw the
Dipsacus_fullonum added a comment.
I don't understand why this doesn't have high priority. It makes the functions mw.wikibase.getLabel( id ), mw.wikibase.getDescription( id ), and mw.wikibase.getSitelinkl( id ) unreliable for IDs obtained from a module's arguments or from statement
24 matches
Mail list logo