Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Differences:</p> <ol> <li>YAML, depending on how you use it, can be more readable than JSON</li> <li>JSON is often <a href="https://stackoverflow.com/questions/2451732/how-is-it-that-json-serialization-is-so-much-faster-than-yaml-serialization-in-p">faster</a> and is probably still interoperable with more systems</li> <li>It's possible to write a "good enough" JSON parser very quickly</li> <li>Duplicate keys, which are <em>potentially</em> valid JSON, are <em>definitely</em> invalid YAML.</li> <li>YAML has a ton of features, including comments and relational anchors. YAML syntax is accordingly quite complex, and can be hard to understand.</li> <li>It is possible to write recursive structures in yaml: <code>{a: &amp;b [*b]}</code>, which will loop infinitely in some converters. Even with circular detection, a "yaml bomb" is still possible (see <a href="https://en.wikipedia.org/wiki/Billion_laughs" rel="noreferrer">xml bomb</a>).</li> <li>Because there are no references, it is impossible to serialize complex structures with object references in JSON. YAML serialization can therefore be more efficient.</li> <li>In some coding environments, the use of YAML can allow an attacker to <a href="https://pyyaml.org/wiki/PyYAMLDocumentation" rel="noreferrer">execute arbitrary code</a>. </li> </ol> <p>Observations:</p> <ol> <li>Python programmers are generally big fans of YAML, because of the use of indentation, rather than bracketed syntax, to indicate levels. </li> <li>Many programmers consider the attachment of "meaning" to indentation a poor choice.</li> <li>If the data format will be leaving an application's environment, parsed within a UI, or sent in a messaging layer, JSON might be a better choice.</li> <li>YAML can be used, directly, for complex tasks like grammar definitions, and is often a better choice than inventing a new language. </li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the difference between YAML and JSON? When to prefer one over the other
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USErik Aronesty
    1. USErik Aronesty
    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. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould you expand on the third point? I thought it was.
      singulars
      1. PO
      1. USAlexFoxGill
    2. COIt is. The entire purpose of [Yaml 1.2](http://www.yaml.org/spec/1.2/spec.html) was to resolve the few compatibility differences to make JSON a strict subset. If you believe the spec didn't achieve its purpose, Erik, please point to an example somewhere of valid JSON that violates the YAML spec and/or breaks a verified 1.2-compliant YAML parser.
      singulars
      1. PO
      1. USSFEley
    3. CO@SFEley The YAML Spec says there are potentially valid JSON files that would be invalid YAML. But it's not likely in real use. "JSON's RFC4627 requires that mappings keys merely “SHOULD” be unique, while YAML insists they “MUST” be. Technically, YAML therefore complies with the JSON spec, choosing to treat duplicates as an error. In practice, since JSON is silent on the semantics of such duplicates, the only portable JSON files are those with unique keys, which are therefore valid YAML files." - http://www.yaml.org/spec/1.2/spec.html#id2759572
      singulars
      1. PO
      1. USDavid C. Bishop
 

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