Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In my experience, <code>GET /users/{id} GET /users/email/{email}</code> is the most common approach. I would also expect the methods to return a 404 Not Found if a user doesn't exist with the provided <code>id</code> or <code>email</code>. I wouldn't be surprised to see <code>GET /users/id/{id}</code>, either (though in my opinion, it is redundant).</p> <h2>Comments on the other approaches</h2> <ol> <li><code>GET /users/id={id} GET /users/email={email}</code> <ul> <li>I don't think I've seen this, and if I did see it, it would be very confusing. It's almost like it's trying to imitate query parameters with path parameters.</li> </ul></li> <li><code>GET /users?id={id} GET /users?email={email}</code> <ul> <li>I think you hit the nail on the head when you mentioned using query parameters for filtering.</li> <li>Would it ever make sense to call this resource with <em>both</em> an <code>id</code> and an <code>email</code> (e.g. <code>GET /users?id={id}&amp;email={email}</code>)? If not, I wouldn't use a single resource method like this.</li> <li>I would expect this method for retrieving a <em>list</em> of users with optional query parameters for filtering, but I would not expect <code>id</code>, <code>email</code> or any unique identifier to be among the parameters. For example: <code>GET /users?status=BANNED</code> might return a list of banned users.</li> </ul></li> </ol> <p><sub>Check out <a href="https://stackoverflow.com/a/4028874/1671856">this answer</a> from a related question.</sub></p>
    singulars
    1. This table or related slice is empty.
    1. POREST API DESIGN - Getting a resource through REST with different parameters but same url pattern
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USDannyMo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POREST API DESIGN - Getting a resource through REST with different parameters but same url pattern
      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. COThank you for the input. Actually you are right. It seems like I read #1 in the "RESTful java with Jax-rs" book but somewhat out of context. But I very clearly remember reading that as an answer to one of the questions on stackoverflow itself (believe me when I say I am trying very hard to find that link to prove to my colleagues too :) ) and #2 is exactly what I was looking for. Some feedback on the design. Thank you!
      singulars
      1. PO
      1. USshahshi15
    2. COPS: I am not sure if posting this is against the rule here but you can probably throw some light on one of my other questions as well? please? :) http://stackoverflow.com/questions/20508008/scim-endpoints-and-other-extended-resources-in-scim
      singulars
      1. PO
      1. USshahshi15
 

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