Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Edit:</p> <p>After thinking about it a bit more, I'm inclined to agree that Range headers aren't appropriate for pagination. The logic being, the Range header is intended for the server's response, not the applications. If you served 100 megabytes of results, but the server (or client) could only process 1 megabyte at a time, well, thats what the Range header is for.</p> <p>I'm also of the opinion that a subset of resources is its own resource (similar to relational algebra.), so it deserve representation in the URL.</p> <p>So basically, I recant my original answer (below) about using a header.</p> <hr> <p>I think you answered your own question, more or less - return 200 or 206 with content-range and optionally use a query parameter. I would sniff the user agent and content type and, depending on those, check for a query parameter. Otherwise, require the range headers.</p> <p>You essentially have conflicting goals - let people use their browser to explore (which doesn't easily allow custom headers), or force people to use a special client that can set headers (which doesn't let them explore).</p> <p>You could just provide them with the special client depending on the request - if it looks like a plain browser, send down a small ajax app that renders the page and sets the necessary headers.</p> <p>Of course, there is also the debate about whether the URL should contain all the necessary state for this sort of thing. Specifying the range using headers can be considered "un-restful" by some.</p> <p>As an aside, it would be nice if servers could respond with a "Can-Specify: Header1, header2" header, and web browsers would present a UI so users could fill in values, if they desired.</p>
    singulars
    1. This table or related slice is empty.
    1. POPaging in a Rest Collection
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRichard Levasseur
    1. USRichard Levasseur
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the response. I've thought about the topic, but was hoping to get a second opinion. Happen to have a pointer for the header arguments?
      singulars
      1. PO
      1. USKarl Guertin
    2. COHere's the only one i have bookmarked (see the discussion in the comments): http://barelyenough.org/blog/2008/05/versioning-rest-web-services/ Another site revolved around Ruby's usage of .json, .xml, .whatever in determining the content type of a request. Some of the examples: * language - putting it in the URL means sending the link to another country would render it in the wrong language. * pagination - Putting it in the header means you can't link people to what you see
      singulars
      1. PO
      1. USRichard Levasseur
    3. CO* content-type: a combination of language and pagination problems - if its in the url, what if the client doesn't support that content type (eg, a .ajax and a .html extension)? Conversely, without that content-type in the url, you can't ensure the same representation is given. "new ajax site! example.com/cool.ajax" vs "cool article here: example.com/article.ajax#id=123".
      singulars
      1. PO
      1. USRichard Levasseur
 

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