Closed joni-herttuainen closed 1 year ago
I have a possible (and straightforward) solution: keep the query as given when rewrite=False
, specifically the limit
and offset
parameters, and print a warning if any of these parameters is passed to the method, announcing they won't be taken into account because rewrite
was set to False
.
Also, it would be good to not have any limit, and just use what is given in the query, or even have an option to not have a limit.
Issue When doing a
sparql(..., rewrite=False)
call, theLIMIT
written in the query string is not reinforced, it needs to be manually fed as a keyword argument. Is this the expected behavior?I would have expected that
rewrite=False
would guarantee the query string is not manipulated.This seems to affect at least the latest release and the current version in master.
Repro
Debug output:
To get what I expected: