Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Like this, for example:</p> <pre><code>public HttpResponseMessage Post(Person person) { if (ModelState.IsValid) { PersonDB.Add(person); return Request.CreateResponse(HttpStatusCode.Created, person); } else { // the code below should probably be refactored into a GetModelErrors // method on your BaseApiController or something like that var errors = new List&lt;string&gt;(); foreach (var state in ModelState) { foreach (var error in state.Value.Errors) { errors.Add(error.ErrorMessage); } } return Request.CreateResponse(HttpStatusCode.Forbidden, errors); } } </code></pre> <p>This will return a response like this (assuming JSON, but same basic principle for XML):</p> <pre><code>HTTP/1.1 400 Bad Request Content-Type: application/json; charset=utf-8 (some headers removed here) ["A value is required.","The field First is required.","Some custom errorm essage."] </code></pre> <p>You can of course construct your error object/list any way you like, for example adding field names, field id's etc.</p> <p>Even if it's a "one way" Ajax call like a POST of a new entity, you should still return something to the caller - something that indicates whether or not the request was successful. Imagine a site where your user will add some info about themselves via an AJAX POST request. What if the information they have tried to entered isn't valid - how will they know if their Save action was successful or not?</p> <p>The best way to do this is using <strong>Good Old HTTP Status Codes</strong> like <code>200 OK</code> and so on. That way your JavaScript can properly handle failures using the correct callbacks (error, success etc).</p> <p>Here's a nice tutorial on a more advanced version of this method, using an ActionFilter and jQuery: <a href="http://asp.net/web-api/videos/getting-started/custom-validation">http://asp.net/web-api/videos/getting-started/custom-validation</a> </p>
    singulars
    1. This table or related slice is empty.
    1. POHandle ModelState Validation in ASP.NET Web API
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USShaun Wilson
    1. USAnders Arpi
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COThat just returns my `enquiry` object, it doesn't say which properties are invalid though? So If I left `CustomerAccountNumber` empty, it should say the default validation message (CusomterAccountNumber field is required..)
      singulars
      1. PO
      1. USCallumVass
    2. COEdited my answer.
      singulars
      1. PO
      1. USAnders Arpi
    3. COI see, so is this the "correct" way of handling Model Validation then? Seems a bit messy to me..
      singulars
      1. PO
      1. USCallumVass
 

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