Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to define how you're going to treat "credits" in your system; it matters whether or not you intend to define them as resources or as an attribute of your customer resource.</p> <p>In the examples below, I'm going to use XML to represent the resources/entities. This may work for you, but you'll need to have some consistent way of representing your resources in requests and responses - this will help you avoid using query parameters (e.g. <a href="http://example.com" rel="nofollow noreferrer">http://example.com</a>?<em>foo=bar</em>) to define data that belongs in the request body.</p> <p>A couple of ways of representing credits:</p> <ol> <li><p>If a "credit" is <strong>an attribute</strong> of your "customer":</p> <pre><code>&lt;customer id="21"&gt; &lt;balance&gt;10&lt;/balance&gt;&lt;!-- aka credit --&gt; &lt;/customer&gt; </code></pre> <p>Then you might as well just GET the customer, update the credit/balance with your client, and then PUT the <code>&lt;customer&gt;</code> back to <code>/customer/21</code>.</p></li> <li><p>If a "credit" is <strong>its own resource</strong>:</p> <p>You can POST the following to <code>/credit</code>:</p> <pre><code>&lt;credit&gt; &lt;dateApplied&gt;2009-10-15 15:00:00&lt;/dateApplied&gt; &lt;customer href="/customer/21"/&gt; &lt;amount&gt;5&lt;/amount&gt; &lt;/credit&gt; </code></pre> <p>Or you can POST the following to <code>/customer/21/credits</code> (assuming that URI is a list of all of the <code>&lt;credit&gt;</code>s applied to the customer):</p> <pre><code>&lt;credit&gt; &lt;dateApplied&gt;2009-10-15 15:00:00&lt;/dateApplied&gt; &lt;amount&gt;5&lt;/amount&gt; &lt;/credit&gt; </code></pre> <p>This would "append" a new <code>&lt;credit&gt;</code> to the existing list. And also eliminates the need to provide the <code>&lt;customer&gt;</code> in the entity, since it's already present in the URI.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POUpdating a value RESTfully with Post
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRob Hruska
    1. USRob Hruska
    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. 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
    1. COAh, yes, it could be that I don't correctly understand what is and is not a resource. Assuming the first option you present, I think I would run into concurrency issues. If client 1 gets, client 2 gets, client 1 updates, client 2 updates. You're going to have a problem.
      singulars
      1. PO
      1. USpondermatic
    2. CO@NG - Yes, in a multithreaded environment you'll need to manage this. As an example, you could use some sort of locking mechanism, where clients capture and release locks on a given customer. You could also use the second option, which would help you avoid it since each addition of a credit can be summed on the server, instead of making the clients sum the balance.
      singulars
      1. PO
      1. USRob Hruska
    3. COI think it makes sense to post to either a *credit* or *credits* resource. If you PUT the updated customer back, then what happens if more than one client reads and PUTs at the same time? One of their updates will be lost.
      singulars
      1. PO
      1. USctford
 

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