Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I haven't really used web RPC systems (WSDL/Soap), but i think the 'interface document' is there mostly to allow client libraries to create the service API, right? if so, REST shouldn't need it, because the verbs are already defined and don't really need to be documented again.</p> <p>AFAIUI, the REST way is to document the structure of each resource (usually encoded in XML or JSON). In that document, you'll also have to document the relationship between those resources. In my case, a resource is often a container of other resources (sometimes more than one type), therefore the structure doc specifies what field holds a list of URLs pointing to the contained resources. Ideally, only one unique resource will need a single, fixed (documented) URL. everithing else follows from there.</p> <p>The URL 'style' is meaningless to the client, since it shouldn't 'construct' an URL. Every URL it needs should be already constructed on a resource field. That let's you change the URL structure without changing the client (that has saved tons of time to me). Your URLs can be as opaque or as descriptive as you like. (personally, i don't like text keys or slugs; my keys are all BIGINTs or UUIDs)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to solve two REST problems: the interface document; loss of privacy in descriptive URLs
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJavier
    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. COI understand the concepts mentioned above, except your last parenthetical comment. How exactly do you use keys and slugs in this context? The main point of my original question is that, in REST, one does not have and cannot have a flat API or flat interface in general to the service. One must drill, and retain state in the client, if one wants to drill again efficiently to the save resources. We have a graph of pages each containing embedded links to (names of) other resources.
      singulars
      1. PO
      1. USShaping
    2. COyou put an example of a 'descriptive' URL: `/resources/../customer/Madonna/phonenumber` where the customer is keyed by a textstring ('Madonna'). some frameworks have all the facilities in place to make such text keys easy to use; but in REST the aesthetics of the URL is immaterial because they're for machine consumption only. so i simply use internal numeric IDs to build the URLs
      singulars
      1. PO
      1. USJavier
    3. COUsing a numeric ID is how you would make the URL opaque, but REST says that you are to create a self-describing URI-space for all resources first. The machine doesn't care either way--descriptive or opaque--but with a set of opaque URLs how then does a client use the service when he can't read and understand the names of the resources and their semantic value? Also, there still remains the issue of having to explain to your client that he must also write a crawler to look through the resource graph to find specific resources. Can anyone answer this question?
      singulars
      1. PO
      1. USShaping
 

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