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
This is Issue 141 moved from a Google Code project.
Added by 2010-10-25T17:18:25.000Z by gsta...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).
Original labels: Type-Defect, Priority-Medium, v0.9.24
Original description
From the docs:
POST
Execute a SQL command against the database. Returns the records affected or the list of records for queries. In the future other languages will be supported.
Syntax: http://<server>:[<port>]/command/<database>/sql
content: <command-text>
Reality:
It behaves like a GET request like this:
POST http://<server>:[<port>]/command/sql/<database>/<query>
So not only the syntax is incorrect in the docs ('sql' comes first, then <database>) it also requires the whole sql query to be in line with the uri. I'd expect it to behave like the 'query' function where it gets the content in the body like a normal POST request.
Also, while all the other functions are accessible with inserting a Basic auth in the headers, this one doesn't, and requires you to firstly grab the cookie from a 'connect' or other function inserted in the headers for it to function, otherwise throws a 401. Is this on purpose?
The text was updated successfully, but these errors were encountered:
This is Issue 141 moved from a Google Code project.
Added by 2010-10-25T17:18:25.000Z by gsta...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).
Original labels: Type-Defect, Priority-Medium, v0.9.24
Original description
The text was updated successfully, but these errors were encountered: