Re: generic options for explain - Mailing list pgsql-hackers

From Massa, Harald Armin
Subject Re: generic options for explain
Date
Msg-id e3e180dc0905250815h2f1f4a6y4846d8902143028c@mail.gmail.com
Whole thread Raw
In response to Re: generic options for explain  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<br /><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204);
margin:0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> The impression I have is that (to misquote Churchill) XML is the
worst<br/> option available, except for all the others.  We need something that can<br /> represent a fairly complex
datastructure, easily supports addition or<br /> removal of particular fields in the structure (including fields not<br
/>foreseen in the original design), is not hard for programs to parse,<br /> and is widely supported --- ie, "not hard"
includes"you don't have to<br /> write your own parser, in most languages".  How many realistic<br /> alternatives are
there?<br/><br /></blockquote></div>One realistic alternative may be JSON: parsers for nearly all languages are freely
available;everything web-affected speeks it perfectly; it's easier on the eye then XML, less bytes per information,
additionand removal of fields as well as complex structures are possible.<br /><br />Harald<br /><br /><br /><br
clear="all"/><br />-- <br />GHUM Harald Massa<br />persuadere et programmare<br />Harald Armin Massa<br />Spielberger
Straße49<br />70435 Stuttgart<br />0173/9409607<br />no fx, no carrier pigeon <br />-<br />LASIK good, steroids bad?<br
/>

pgsql-hackers by date:

Previous
From: Joshua Tolley
Date:
Subject: Re: generic options for explain
Next
From: Michael Meskes
Date:
Subject: Re: Warnings in compile