-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.set("val").sparql may result in DELETE DATA query with variables #352
Comments
Thanks for creating the issue! Happy to accept a PR which makes sure a |
Hi, Jesse! |
I'm happy for you to branch off this commit where CI is passing. The subsequent dependabot commits need to be reverted as the upgrade to @rdfjs/data-model v2 (which is ESM only) is what broke things in the first place. |
Once you create a PR I'll revert those commits on main, and manually do relevant upgrades once merging your work. |
From what I reckon also vars are disalowed in INSERT DATA. |
To elaborate on the reason why it guards against The statement On the other hand |
Paths, such as:
May result in DELETE DATA queries with variables, such as:
Which is okay by LDFlex, as seen in this test.
However, as per the spec, variables are not allowed in DELETE DATA queries, and other query engines that are more strictly conformant to the spec may fail to execute such queries, e.g., Comunica fails with:
Perhaps having such paths result in
DELETE ... WHERE ...
would make LDFlex more conformant with the spec and allow their execution by other engines.Environment:
"@ldflex/comunica": "^5.0.1",
"ldflex": "^2.15.2",
"@comunica/query-sparql": "^2.6.9",
The text was updated successfully, but these errors were encountered: