Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>IMHO, there is one big reason everyone sticks with SOAP instead of using JSON. With every JSON setup, you're always coming up with your own data structure for each project. I don't mean how the data is encoded and passed, but how the data format is defined, the data model.</p> <p>SOAP has an industry mature way of specifying that data will be in the form Cart is a collection of Products and each product can have these attributes, etc. A well put together WSDL document really has this nailed. Heck, it's a W3C specification.</p> <p>JSON has similar ways of specifying this data structure. A JavaScript class comes to mind as the most common way of doing this. A JavaScript class isn't really a data structure in any kind of agnostic, well established, widely used way. Heck, JavaScript really only executes in one environment, the browser.</p> <p>In short, SOAP as a way of specifying the data structure in a maturely formatted document (WSDL). JSON doesn't.</p> <p><strong>UPDATE</strong>: I have to say, I'm amazed by the number of down-votes this answer has gotten over the years esp given its accuracy at the time. I don't mean to hate on JSON, but after <a href="http://metajack.im/2010/02/01/json-versus-xml-not-as-simple-as-you-think/" rel="nofollow noreferrer">reading a recent article</a>, I continue to stand by my previously made points. Meanwhile, JSON-RPC seems to be practically abandoned from a standardized format perspective (version 2.0 a proposal from 2010) and no other JSON protocols seemingly close to the level of SOAP's standardization. (Personally, this hasn't stopped me from embracing JSON-RPC 2.0 in production environments. I just would never use it in a proposal to a Fortune 500 company.)</p> <p>To be clear, from an internal use perspective, JSON is GREAT. Lightweight. Fast. Widely used. Reasonably human-readable. But for enterprise, where multiple data streams are frequently merged. And data format specification between dozens of departments is necessary. XML is the established leader.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy use SOAP over JSON and custom data format in an "ENTERPRISE" application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuserx
    1. USuserx
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy use SOAP over JSON and custom data format in an "ENTERPRISE" application?
      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. COBlah, see this question and answer. http://stackoverflow.com/questions/3538131/is-there-a-wsdl-like-mechanism-for-json
      singulars
      1. PO
      1. USjvenema
    2. CO@jvenema - Just because it exists doesn't make it mature ;) As time goes on and developers continue to prefer JSON, this of course has / will change. Personally, I don't see a major reason to go JSON over XML. The only major advantage is data size (which is rapidly becoming less of a concern). Any reasonable consumer of XML or JSON data implements a parser anyways negating the benefit of JSON being JavaScript native. Arguably it is SLIGHTLY easier and faster to parse JSON. I'm not sure this mandates the industry wide change that some developers seem to demand.
      singulars
      1. PO
      1. USuserx
    3. COfair point, but how would JSON change in the future? It's the simplest spec in the word - http://www.json.org/. Compare that to the SOAP spec (for part 1 of 4, see http://www.w3.org/TR/2007/REC-soap12-part1-20070427/) and the benefits of simplicity become obvious. (P.S., JavaScript has very little to do with JSON, other than they're somewhat similar in structure, so all the discussion about JavaScript classes are moot).
      singulars
      1. PO
      1. USjvenema
 

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