Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My advice would be this:</p> <pre><code>/garages Returns list of garages (think JSON array here) /garages/yyy Returns specific garage /garage/yyy/cars Returns list of cars in garage /garages/cars Returns list of all cars in all garages (may not be practical of course) /cars Returns list of all cars /cars/xxx Returns specific car /cars/colors Returns lists of all posible colors for cars /cars/colors/red,blue,green Returns list of cars of the specific colors (yes commas are allowed :) ) </code></pre> <p>Edit:</p> <pre><code>/cars/colors/red,blue,green/doors/2 Returns list of all red,blue, and green cars with 2 doors. /cars/type/hatchback,coupe/colors/red,blue,green/ Same idea as the above but a lil more intuitive. /cars/colors/red,blue,green/doors/two-door,four-door All cars that are red, blue, green and have either two or four doors. </code></pre> <p>Hopefully that gives you the idea. Essentially your Rest API should be easily discoverable and should enable you to browse through your data. Another advantage with using URLs and not query strings is that you are able to take advantage of the native caching mechanisms that exist on the web server for HTTP traffic.</p> <p>Here's a link to a page describing the evils of query strings in REST: <a href="http://web.archive.org/web/20070815111413/http://rest.blueoxen.net/cgi-bin/wiki.pl?QueryStringsConsideredHarmful" rel="nofollow noreferrer">http://web.archive.org/web/20070815111413/http://rest.blueoxen.net/cgi-bin/wiki.pl?QueryStringsConsideredHarmful</a></p> <p>I used Google's cache because the normal page wasn't working for me here's that link as well: <a href="http://rest.blueoxen.net/cgi-bin/wiki.pl?QueryStringsConsideredHarmful" rel="nofollow noreferrer">http://rest.blueoxen.net/cgi-bin/wiki.pl?QueryStringsConsideredHarmful</a></p>
    singulars
    1. This table or related slice is empty.
    1. PORESTful URL design for search
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLie Ryan
    1. USJustin Bozonier
    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 detailed answer. On the last one, what if I want to search by both color and number of doors? /cars/colors/red,blue,green/doors/4 That doesn't seem right.
      singulars
      1. PO
      1. USParand
    2. COCommas in the URL don't feel right to me, but still valid rest. I think it is just a paradigm shift.
      singulars
      1. PO
      1. USJustin Bozonier
    3. COI don't like this suggestion. How would you know the difference between `/cars/colors/red,blue,green` and `/cars/colors/green,blue,red` ? The path element of the URI should be hierarchical, and I don't really see that being the case here. I think this is a situation where the query-string is the most appropriate choice.
      singulars
      1. PO
      1. UStroelskn
 

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