Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h1>NO</h1> <p>Personal experience. YAML seems a wonderful idea and I loved it and its simplicity. Then I started investing time on it: the very same concept of being able to read it in a language and write in another was very enticing, but... cutting it short, it turned up to be <strong>a mere illusion</strong>, unsubstantiated by facts.</p> <p><strong>Every implementation of YAML differs too much from the other ones</strong>.</p> <ul> <li>Arrays, automatically serialized by one, cannot sometimes be read by another.</li> <li><p>Cross references are supported, but their implementation is really sketchy. </p> <p>References are powerful, but: </p> <ul> <li>They are quite <em>limited</em> for some hardcore application.</li> <li>They represent an <em>overkill</em> to most low-end YAML-based projects. </li> </ul> <p><br>So, frequently, they are ignored, <em>and errored upon</em>, by most parsers.</p></li> </ul> <p>Summing it up, the standard isn't well set.</p> <p>There are core concepts that are nice and simple, but the actual standard document is full of details about <strong>features that most people don't want to use and are difficult and expensive to implement</strong>.</p> <p>There <strong>isn't</strong> a distinction of <strong>levels of compatibility</strong>, like there is in DOM (DOM level 1, DOM level 2, etc) so every parser implementor implements what he feels like to, to the extent he can bear, then drops it and it's <strong>hard to discern what works and what doesn't</strong>.</p> <h2>Use Alternatives</h2> <ul> <li><p><strong>JSON</strong> if you value the <strong><em>cross language data exchange language</em></strong> and <strong><em>little redundancy</em></strong> aspects as the top priority</p></li> <li><p><strong>INI</strong> if you value <strong><em>performance and backward compatibility</em></strong> (<em>on PHP</em>, as <code>parse_ini_file()</code> is fast, and there since... always) and <strong><em>readability/editability by humans</em></strong>, instead.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POShould I use YAML for Config Files in a PHP Application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USZJR
    1. USZJR
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShould I use YAML for Config Files in a PHP 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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'd like to throw out that there are libraries like Spyc library which do a great job of parsing YAML files.
      singulars
      1. PO
      1. USJimbo
    2. CO+1 for 'levels of compatibility'
      singulars
      1. PO
      1. USBasel Shishani
 

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