You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the BETWEEN keyword, if a sloppy user miswrite the start date in a way it becomes a date past the given end date of that interval, BW should return an error warning the user about it instead of silently returning an empty result (as it is the case nowadays, which is a little misleading).
To illustrate, given the query below:
SELECT ?p, ?o
FROM ?test
WHERE {
/u<peter> ?p ?o
}
BETWEEN 2016-04-01T00:00:00-08:00, 2016-02-01T00:00:00-08:00;
The query nowadays just silently returns an empty result:
Result:
OK
Which can be misleading for the user as it will make she believe that the given interval is valid and there are no triples in the ?test graph satisfying it, whereas the truth is that the typed interval is not valid (which should be pointed as an error) as the user miswrote something while typing it.
The text was updated successfully, but these errors were encountered:
When using the
BETWEEN
keyword, if a sloppy user miswrite the start date in a way it becomes a date past the given end date of that interval, BW should return an error warning the user about it instead of silently returning an empty result (as it is the case nowadays, which is a little misleading).To illustrate, given the query below:
And a
?test
graph with triples:The query nowadays just silently returns an empty result:
Which can be misleading for the user as it will make she believe that the given interval is valid and there are no triples in the
?test
graph satisfying it, whereas the truth is that the typed interval is not valid (which should be pointed as an error) as the user miswrote something while typing it.The text was updated successfully, but these errors were encountered: