Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have the same problem with ASP.Net WebAPI, so I don't think this is so much a ServiceStack issue, but just a general concern with dealing with Raven style id's on a REST URL.</p> <p>For example, let's say I query <code>GET: /api/users</code> and return a result like:</p> <pre><code>[{ Id:"users/1", Name:"John" }, { Id:"users/2", Name:"Mary" }] </code></pre> <p>Now I want to get a specific user. If I follow pure REST approach, the Id would be gathered from this document, and then I would pass it in the id part of the url. The problem here is that this ends up looking like <code>GET: /api/users/users/1</code> which is not just confusing, but the slash gets in the way of how WebAPI (and ServiceStack) route url parameters to action methods.</p> <p>The compromise I made was to treat the id as an integer from the URL's perspective only. So the client calls <code>GET: /api/users/1</code>, and I define my method as <code>public User Get(int id)</code>.</p> <p>The cool part is that Raven's <code>session.Load(id)</code> has overloads that take either the full string form, or the integer form, so you don't have to translate most of the time.</p> <p>If you DO find yourself needing to translate the id, you can use this extension method:</p> <pre><code>public static string GetStringIdFor&lt;T&gt;(this IDocumentSession session, int id) { var c = session.Advanced.DocumentStore.Conventions; return c.FindFullDocumentKeyFromNonStringIdentifier(id, typeof (T), false); } </code></pre> <p>Calling it is simple as <code>session.GetStringIdFor&lt;User&gt;(id)</code>. I usually only have to translate manually if I'm doing something with the id other than immediately loading a document.</p> <p>I understand that by translating the ids like this, that I'm breaking some REST purist conventions, but I think this is reasonable given the circumstances. I'd be interested in any alternative approaches anyone comes up with.</p>
    singulars
    1. This table or related slice is empty.
    1. POServiceStack Routing with ravendb ids
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMatt Johnson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POServiceStack Routing with ravendb ids
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for this Matt. So are you returning an Integer ID from GET:/api/users?
      singulars
      1. PO
      1. USChris
    2. CONo, I found it too clumsy to manipulate the result set, so I just return the full string Id. The client app keeps the full string id, but when it builds a url with an id, it strips off the front part using something like id.split("/")[1]
      singulars
      1. PO
      1. USMatt Johnson
 

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