Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POApp Engine : 400 - Your client has issued a malformed or illegal request
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDrew Sears
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POApp Engine : 400 - Your client has issued a malformed or illegal request
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi Drew - thanks for highlighting this - definitely looks like the cause of the problem. It strikes me as an incredibly naive constraint - especially since it's not mandated by the spec. Regardless of my use case, DELETE is quite a complex operation - e.g. are we performing a hard delete or a soft delete - what about archiving? Surely it should be up to the serving application (and not the context unaware web server) to determine 200 or 400 in this situation. Will follow this up on the google issue which appears to have been re-opened based on similar concerns. Thx.
      singulars
      1. PO
      1. UShawkett
    2. COWhy not just follow the convention? GET/PUT/DELETE should fetch, create/overwrite, or remove the exact resource identified by the URI. Extra parameters for all 3 should go on the query string. Only PUT should have a body, and it should be the resource contents. If you DELETE a URI and return a 200, a subsequent GET or DELETE should 404. For everything else, there's POST, which just means "send some stuff to this URI and expect something to happen". If you wanted to delete two resources at once, it would be more appropriate to do that in a POST than trying to stuff the logic into a DELETE.
      singulars
      1. PO
      1. USDrew Sears
    3. COA few points - 1) if data should be encoded on the query string, then jQuery's impl of DELETE is broken. 2) POST should be used to create an entity subordinate to the resource indicated in the URI - I'm doing nothing even close to that - POST would be a big hack. 3) PUT doesn't use query params by convention, any more than DELETE doesn't have a body 4) I can't find any official statement that a request body is unexpected for DELETE - the author at your link seems to have embellished the specification. All that said, it looks like query string params are my best bet. Just not liking it :) Thx
      singulars
      1. PO
      1. UShawkett
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload