Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html" rel="noreferrer">The spec</a> does not explicitly forbid or discourage it, so I would tend to say it is allowed.</p> <p>Microsoft sees it the same way (I can hear murmuring in the audience), they state in the MSDN article about the <a href="https://web.archive.org/web/20090213142728/http://msdn.microsoft.com:80/en-us/library/cc716657.aspx" rel="noreferrer">DELETE Method of ADO.NET Data Services Framework</a>:</p> <blockquote> <p>If a DELETE request includes an entity body, the body is ignored [...]</p> </blockquote> <p>Additionally here is what <a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html" rel="noreferrer">RFC2616</a> (HTTP 1.1) has to say in regard to requests:</p> <ul> <li>an <em>entity-body</em> is only present when a <em>message-body</em> is present (section 7.2)</li> <li>the presence of a <em>message-body</em> is signaled by the inclusion of a <code>Content-Length</code> or <code>Transfer-Encoding</code> header (section 4.3)</li> <li>a <em>message-body</em> must not be included when the specification of the request method does not allow sending an <em>entity-body</em> (section 4.3)</li> <li>an <em>entity-body</em> is explicitly forbidden in TRACE requests only, all other request types are unrestricted (section 9, and 9.8 specifically)</li> </ul> <p>For responses, this has been defined:</p> <ul> <li>whether a <em>message-body</em> is included depends on both request method <em>and</em> response status (section 4.3)</li> <li>a <em>message-body</em> is explicitly forbidden in responses to HEAD requests (section 9, and 9.4 specifically)</li> <li>a <em>message-body</em> is explicitly forbidden in 1xx (informational), 204 (no content), and 304 (not modified) responses (section 4.3)</li> <li>all other responses include a message-body, though it may be of zero length (section 4.3)</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POIs an entity body allowed for an HTTP DELETE request?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTomalak
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs an entity body allowed for an HTTP DELETE 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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Jason Definitely. You could also use custom headers to pass additional data, but why not use the request body.
      singulars
      1. PO
      1. USTomalak
    2. COAlthough the spec does not forbid DELETE requests from having a message-body, [section 4.3](http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.3) seems to indicate that _the body should be ignored by servers_ since there are no "defined semantics" for [DELETE](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.7) entity-bodies: "A server SHOULD read and forward a message-body on any request; **if the request method does not include defined semantics for an entity-body, then the message-body SHOULD be ignored when handling the request**."
      singulars
      1. PO
      1. USshelley
 

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