Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>URIs are references to resources, not the resources themselves. In a sense, they are all canonical. Different URIs may identify the same resource. They may also be pleceholders for something that doesn't even exist yet. The "one cannot exist without the other" concept is something specific to the application, it's not a REST constraint. Ideally, you won't have URIs depending on each other. If you delete the resource all URIs pointing to it will point to nothing. Or at least that's how things should be if the URIs were pointing to resources and not to one another.</p> <p><strong>UPDATE:</strong></p> <p>According to <a href="https://www.ietf.org/rfc/rfc2396.txt" rel="nofollow">RFC2396</a>:</p> <blockquote> <p>1.1 Overview of URI:</p> <p>...</p> <p>Resource</p> <p>A resource can be anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources. Not all resources are network "retrievable"; e.g., human beings, corporations, and bound books in a library can also be considered resources.</p> <p><strong>The resource is the conceptual mapping to an entity or set of entities</strong>, not necessarily the entity which corresponds to that mapping at any particular instance in time. Thus, a resource can remain constant even when its content---the entities to which it currently corresponds---changes over time, provided that the conceptual mapping is not changed in the process.</p> <p>Identifier</p> <p><strong>An identifier is an object that can act as a reference to something that has identity.</strong> In the case of URI, the object is a sequence of characters with a restricted syntax.</p> </blockquote> <p><strong>UPDATE:</strong></p> <p>I guess, if the resource is accessible/modifiable through multiple URIs, it's up to the application to designate a canonical one (the URI that is going to be included in the hypertext of responses). But yes, it's the URIs that are non-canonical (from the application's point of view), not the resources.</p>
    singulars
    1. This table or related slice is empty.
    1. POREST: Deleting non-canonical resources
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USank
    1. USank
    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. CO`URIs are references to resource representations, not the resources themselves`. Wikipedia disagrees: http://en.wikipedia.org/wiki/Uniform_resource_identifier
      singulars
      1. PO
      1. USGili
    2. COThe key point I was trying to get across is that URIs are references to **resources** not resource **representations**. A **representation** in the context of REST is the request/response entity body. I assume this isn't what you had in mind?
      singulars
      1. PO
      1. USGili
    3. CO`they are all canonical`. No. Multiple canonical URIs cannot point to the same resource. Multiple non-canonical URIs can. `one cannot exist without the other [...] is something specific to the application`: Good point. So you're saying both are just non-canonical URIs except that one can be removed and the other can't (due to application-specific constraints).
      singulars
      1. PO
      1. USGili
 

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