Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow does JSON compare to XML in terms of file size and serialisation/deserialisation time?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMarcelo Cantos
    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. VTDownMod
    1. COI don't agree with this general statement. I can write an equivalent XML doc that is more compact than JSON, if I confine myself to using attributes. If I use more of the power of XML, as you said, using both attributes and elements, the XML document will become larger than the original JSON document, but it also holds the potential to convey more meaning. It's wrong to flatly state, "JSON is smaller". It isn't. Common use of JSON is smaller than common use of XML (where everything is an element), but the common use is not required.
      singulars
      1. PO
      1. USCheeso
    2. CO@Cheeso: Firstly, common use is the only thing that counts in the real world. Secondly, I suspect that only way to make XML smaller is to violate recommended practice such as not using attributes to store content. See [here](http://www.ibm.com/developerworks/xml/library/x-eleatt.html) for an exposition of some of the principles of XML design, with authoritative supporting references; note how verbose the final example is. An equivalent JSON might be: `{"menu":[{"portion":[250,"mL"], "name":"Small soft drink"}, {"portion":[500,"g"], "name":"Sirloin steak"}]}`.
      singulars
      1. PO
      1. USMarcelo Cantos
    3. CO@Marcelo, regarding common use, I don't agree with your viewpoint. How other people format their XML has no bearing on whether I can or should use it in server-to-browser communication in *my* app. Aso, regarding the article, it's fine to make recommendations, but what weight do they hold in this particular case? Why follow them? As I said in my full answer, if you force the XML to be verbose, it will be verbose. If you allow yourself to use the more succint XML usage, then it will be comparable with JSON in length.
      singulars
      1. PO
      1. USCheeso
 

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