Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your these urls seem fine :</p> <blockquote> <p><a href="http://example.com/cases" rel="nofollow">http://example.com/cases</a> (and with id for a single case)</p> <p><a href="http://example.com/cases/" rel="nofollow">http://example.com/cases/</a>{id}/users (same idea as above)</p> <p><a href="http://example.com/cases/" rel="nofollow">http://example.com/cases/</a>{id}/messages (same idea as above)</p> </blockquote> <p>In terms of your related data and how to query them, I'd suggest that first of all you should decide on the return data structure, considering the fact that in both cases you are returning "messages" (although containing somewhat different data). What I would do is, I would have a common json structure for both related resources urls something along the lines of </p> <blockquote> <p>{"sender": "an user test",</p> <p>"receiver": "an user test4",</p> <p>"amount_messages": 3,</p> <p>"timestamp": 12312421424}</p> </blockquote> <p>And my resource urls would look somewhat like this:</p> <blockquote> <p>GET <a href="http://example.com/cases/" rel="nofollow">http://example.com/cases/</a>{id}/messages</p> <p>GET <a href="http://example.com/cases/" rel="nofollow">http://example.com/cases/</a>{id}/messages?receiver=testuser1&amp;sender=testuser2</p> </blockquote> <p>I don't understand the reason for that "/analysis" in the url. It's a bit more redundant (unless ofcourse there is a very specific reason for it). The clients who are going to use your apis are expecting the return data to be generic, especially when they are trying to do filter queries on the same resource. In your case, we are either listing "message traffic" (which I would call listing "all messages") OR listing "message traffic" WHERE sender is FOO and receiver is BAR (which I would call filtering the "all messages" data by sender and receiver information.</p> <p>Keeping the return data model consistent helps client developers to generate POJOs (in java land) and/or consistent data models on their side as well. </p> <p>I hope this helps ! good luck!</p>
    singulars
    1. This table or related slice is empty.
    1. POREST resource related data
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USshahshi15
    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. This table or related slice is empty.
    1. COMy examples are about messages, but it can return all related calculated data of related resources of a "case". All these calculated data results are returned as generic as possible, but the results are aimed to create analysis tools (like graphs and stuff). For every graph-style they need another results. That's why I seperated this for every case by: _/analysis/a-graph-data-result-style_
      singulars
      1. PO
      1. USA. Ly
    2. COThat's the point, you shouldn't. As Steve mentioned above, urls should not be declarative. If you want your return types to be graph style related, you could have something like this as well: GET http://example.com/analysis/{graph-style}/cases/{id}/messages?receiver=testuser1&sender=testuser2 Looking at the urls clients can easily determine that the data model might not change (here the data format is always going to be that of "messages") but the data itself will change depending on the graph-style they ask the data for.
      singulars
      1. PO
      1. USshahshi15
    3. COBut in most cases, you, as a service provider, SHOULD NOT have to worry about what kind of graph style the client is implementing. Facebook/Google probably has a gazillion applications developed by clients each implementing their own set of graphs (depending on the usecase ofcourse). If they start providing graph style custom data for EACH client, that wouldn't make sense for any service provider.
      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