Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>"I don't care about metadata; I only care about the data"</p> <p>That's actually a great tagline for JSON Light as a whole :)</p> <p>The core principle of JSON light is that servers can cut down on unnecessary metadata in the payload. When a client does need a certain bit of metadata (for example, the URL it should use to edit the entity), the client can generate that URI itself based on common OData URI conventions.</p> <p>A client can control how much metadata the server should include in the payload by requesting one of the three different metadata levels: </p> <ul> <li>"application/json;odata=fullmetadata" for clients who need to use metadata and don't have a way to compute it themselves</li> <li>"application/json;odata=minimalmetadata" for clients who use metadata but are fine computing it themselves</li> <li>"application/json;odata=nometadata" for clients who don't care about any metadata whatsoever</li> </ul> <p>If you're writing a client that really doesn't care about any metadata at all (where metadata includes edit links, entity types, property types, stream information, navigation properties, etc.), then you can request "application/json;odata=nometadata" and you'll just get back a bag of properties.</p> <p>Even if you don't care about metadata, there are lots of little differences between JSON Verbose and JSON Light. I would strongly recommend relying on a library for this if you're in a language where one is available (for example, in .NET there's the WCF Data Services Client and in Javascript there's datajs or jaydata). Here's a list of a couple differences off the top of my head:</p> <ul> <li>In OData v2, DateTimes could be represented using the ticks-based format (e.g., <code>"lastUpdated": "\/Date(1240718400000)\/"</code>), but in v3 JSON only ISO 8601 is supported (e.g., <code>"1992-01-01T00:00:00"</code>)</li> <li>There is no "d" wrapper on results payloads anymore.</li> <li>Instead of a "results" wrapper for collection results, there is now a "value" wrapper</li> <li>Instead of "__count" for inline count, JSON Light uses "odata.count"</li> </ul> <p>As an example, take a look at the differences in the payload produced by this query:</p> <p>http://services.odata.org/v3/OData/OData.svc/Products?$inlinecount=allpages&amp;$top=2&amp;$format=application/json;odata=verbose</p> <p>Versus this:</p> <p>http://services.odata.org/v3/OData/OData.svc/Products?$inlinecount=allpages&amp;$top=2&amp;$format=application/json;odata=nometadata</p>
    singulars
    1. This table or related slice is empty.
    1. POHow would an upgrade from verbose JSON to JSON light affect someone who only looks at the data, and not the metadata?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJen S
    1. USJen S
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow would an upgrade from verbose JSON to JSON light affect someone who only looks at the data, and not the metadata?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Jen. Excellent response. This information helped me realized that I was still referencing WCF Data Services 5.0 instead of the 5.3 that I had installed weeks ago. Doh! I went ahead and downloaded 5.5 and followed some of what I found [here](http://blogs.msdn.com/b/writingdata_services/archive/2012/04/16/upgrading-wcf-data-services-projects-to-wcf-data-services-5-0.aspx) to update. Now `application/json;odata=nometadata` works and I can get to work on making the minimal changes needed in the client code that handles the data. Thanks again.
      singulars
      1. PO
      1. USNate Cook
    2. COis there a doc similar to http://www.odata.org/documentation/odata-v3-documentation/json-verbose-format/ anywhere for light format?
      singulars
      1. PO
      1. USChris DaMour
    3. COThere wasn't really in OData v3, but in OData v4, the JSON format is what we called "JSON light" in v3, with some small modifications. You can find the v4 JSON documentation [here](http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html).
      singulars
      1. PO
      1. USJen S
 

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