From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Invalid YAML output from EXPLAIN |
Date: | 2010-06-07 14:54:38 |
Message-ID: | 4C0D082E.7070002@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Robert Haas wrote:
> On Mon, Jun 7, 2010 at 10:37 AM, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
>
>> Tom Lane wrote:
>> I don't think the above would be particularly hard to implement myself,
>> but if it becomes a really big deal, we can certainly punt by simply
>> quoting anything containing an indicator (the special characters above).
>> It will still be 100% valid YAML, just with some excess quoting for the
>> very rare case when a value contains one of the special characters.
>>
>
> Since you're the main advocate of this feature, I think you should
> implement it rather than leaving it to Tom or I.
>
Or anyone else :-)
> The reason why I was initially skeptical of adding a YAML output
> format is that JSON is a subset of YAML. Therefore, the JSON output
> format ought to be perfectly sufficient for anyone using a YAML
> parser.
>
There is some debate on this point, IIRC.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-07 14:56:40 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Tom Lane | 2010-06-07 14:53:17 | Re: BUG #5490: INSERT doesn't force cast from text to timestamp |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-07 14:56:40 | Re: Invalid YAML output from EXPLAIN |
Previous Message | Robert Haas | 2010-06-07 14:49:29 | Re: Invalid YAML output from EXPLAIN |