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
{{ message }}
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
During one query, if NOW() is bound to a variable in the results, the variable will have as many values as the number of milliseconds taken to execute the query.
Steps to Reproduce:
Create test_query.rq containg:
PREFIX pav: <http://purl.org/pav/>CONSTRUCT {
<> pav:lastUpdateOn ?date .
}
WHERE {
?s?p?o .
BIND(NOW() AS ?date)
}
Execute the following query, you can replace the target with any large enough file: java -jar corese-command-4.5.0.jar sparql -q test_query.rq -i https://raw.githubusercontent.com/Wimmics/IndeGx/main/catalogs/all_catalog_edited.ttl
Expected Behavior:
The result should contain only one binding for NOW(), either at the start of the execution or at the end, at the developer's discretion. This is the behavior expected by the SPARQL 1.1 standard
Note to Developers:
Correcting this bug could slightly speed up querying because this implies a lot of unnecessary calls to the NOW() function.
The text was updated successfully, but these errors were encountered:
Thank you for your report. After testing, we've found that the problem is reproducible and is not limited to the Corese command but affects Corese in general, including all interfaces. We will investigate this further and work on a fix.
remiceres
changed the title
[Bug] Corese-command sparql binds multiples NOW() value in one query
[Bug] Corese sparql binds multiples NOW() value in one query
Jan 11, 2024
The Binding class has been updated to store and retrieve the current time value, allowing the now() function to return the same value during processing. This improves the consistency and reliability of the now() function. Fix#168.
Issue Description:
During one query, if
NOW()
is bound to a variable in the results, the variable will have as many values as the number of milliseconds taken to execute the query.Steps to Reproduce:
test_query.rq
containg:Execute the following query, you can replace the target with any large enough file:
java -jar corese-command-4.5.0.jar sparql -q test_query.rq -i https://raw.githubusercontent.com/Wimmics/IndeGx/main/catalogs/all_catalog_edited.ttl
The result will look something like:
Expected Behavior:
The result should contain only one binding for NOW(), either at the start of the execution or at the end, at the developer's discretion. This is the behavior expected by the SPARQL 1.1 standard
Note to Developers:
Correcting this bug could slightly speed up querying because this implies a lot of unnecessary calls to the
NOW()
function.The text was updated successfully, but these errors were encountered: