Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should put a "complete" representation as your media type defines it. If you're designing your own media type, your specification should define which parts are intended to be mutable and which are intended to be immutable. The Shoji Catalog Protocol, for example, defines <a href="https://bitbucket.org/fumanchu/shoji/src/5f7e3dcaaa725d38c6cd9b202cc205211798134d/spec.txt?at=default#cl-538" rel="nofollow">a "body" member</a> that is intended to contain the mutable data:</p> <blockquote> <p>In general, when a body member is present, processors SHOULD expect the values present within the body to be potentially mutable (via an HTTP PUT or POST, for example) and SHOULD expect any values outside the body member to be immutable; that is, (potentially) writable on insert but not on update. Servers are free, of course to allow or disallow mutability of any part of the resource. But the presence of a "body" member carries with it strong hints regarding the mutability of data both within and without that member.</p> </blockquote> <p>This isn't a standard (although it's so obviously useful to me that I'd like it to become one (wink)). Note that servers are free to do whatever they wish with the representation a client sends; the strongest requirement for any HTTP server is that it attempt to perform the intention of the client (if able and allowed). How and to what extent it does that is really a concern for your particular application, which is why you're not finding much in any specs about it.</p> <p>In practice, I haven't found it useful for the server to validate the links or other immutable parts of a representation; they're simply ignored. That can lead to clients deciding they can omit such. Again, in practice I haven't found that to be a problem.</p>
    singulars
    1. This table or related slice is empty.
    1. POREST resource representation with links, compatible with PUT and GET
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USfumanchu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POREST resource representation with links, compatible with PUT and GET
      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
    1. COThank you. My pencilled-in design includes a "properties" section which looks pretty similar to the idea of the "body" member. I am also considering breaking such things out into their own leaf resources, which would add 5 or 6 resource types to my design (bad), but simplify PUT methods considerably (good)
      singulars
      1. PO
      1. USNeil Slater
 

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