Skip to content
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

Use LSQ to determine UPDATE Queries #229

Open
nck-mlcnv opened this issue Nov 6, 2023 · 2 comments · Fixed by #281
Open

Use LSQ to determine UPDATE Queries #229

nck-mlcnv opened this issue Nov 6, 2023 · 2 comments · Fixed by #281
Assignees
Labels

Comments

@nck-mlcnv
Copy link
Contributor

The SPARQLProtocolWorker should be able to execute UPDATE queries seperately on the given updateEndpoint. For that it needs to know if a query that it's about to execute is an UPDATE query.

@nck-mlcnv
Copy link
Contributor Author

Linked to this issue: #182

@nck-mlcnv nck-mlcnv linked a pull request Sep 23, 2024 that will close this issue
@nck-mlcnv
Copy link
Contributor Author

nck-mlcnv commented Sep 24, 2024

We're not going to use LSQ for this, because integrating it into IGUANA might be a little bit messy and difficulty. Jena should be sufficient.

nck-mlcnv added a commit that referenced this issue Oct 11, 2024
* Add QueryData class

* Check for update queries

* Move responsibility of QueryData to QueryHandler

* Remove unused methods

* Add tests

* Fix authentication

* Cleanup

* Remove unused import statements

* Add chained update request as test case for Update queries distinction

Closes #229
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant