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
Using SELECT 1 + 1 via endpoint gives an error, while via console and studio this works. In the studio it seems to work, as the "command" endpoint is used.
@lvca
This error depends on the endpoint: the command endpoint can do SELECT 1 + 1, while the query endpoint throws the error above. Maybe this becomes fixable given this observation?
It could be dependent on the encoding. While the command gets the query in POST, the query command gets the query in the URL and it must be encoded. Trying to create a test case to reproduce it.
This problem seems to be specific to +. I think this could be related to this comment. However, when using
new URI(text).getPath()
instead of URLDecoder.decode(text, exchange.getRequestCharset()) an unreported exception java.net.URISyntaxException error is reported during compilation. I am not familiar enough with Java or this code base to add a useful exception catch.
The problem with that piece of code is that text is not a URI, but only the command text. Found and fixed the issue. It was the decoding. The text arrives already decoded, so that line not only is not necessary, but it removed the + character.
Activity
gramian commentedon Nov 3, 2022
Likely related to #566 .gramian commentedon Nov 21, 2022
@lvca
This error depends on the endpoint: the
commandendpoint can doSELECT 1 + 1, while thequeryendpoint throws the error above. Maybe this becomes fixable given this observation?lvca commentedon Nov 28, 2022
It could be dependent on the encoding. While the command gets the query in POST, the query command gets the query in the URL and it must be encoded. Trying to create a test case to reproduce it.
[-]Calculator SELECT via endpoint problem[/-][+]Calculator SELECT via query endpoint problem[/+]gramian commentedon Dec 12, 2022
This problem seems to be specific to
+. I think this could be related to this comment. However, when usinginstead of
URLDecoder.decode(text, exchange.getRequestCharset())anunreported exception java.net.URISyntaxExceptionerror is reported during compilation. I am not familiar enough with Java or this code base to add a useful exception catch.Fixed issue with HTTP het /query API and encoding of the command
lvca commentedon Dec 12, 2022
The problem with that piece of code is that text is not a URI, but only the command text. Found and fixed the issue. It was the decoding. The text arrives already decoded, so that line not only is not necessary, but it removed the
+character.chore(studio-deps-dev)(deps-dev): bump enhanced-resolve from 5.21.2 t…
Fixed issue with HTTP het /query API and encoding of the command
chore(studio-deps-dev)(deps-dev): bump enhanced-resolve from 5.21.2 t…
chore(deps): bump the github-actions group across 1 directory with 8 …