Re: Invalid YAML output from EXPLAIN - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Invalid YAML output from EXPLAIN
Date
Msg-id AANLkTikY4fYyGzm-qdWl7YvXUIyqu5gsVCdZGPzRfCI3@mail.gmail.com
Whole thread Raw
In response to Re: Invalid YAML output from EXPLAIN  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Invalid YAML output from EXPLAIN  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Invalid YAML output from EXPLAIN  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-bugs
On Wed, Jun 9, 2010 at 11:03 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Wed, Jun 9, 2010 at 9:35 AM, Dean Rasheed <dean.a.rasheed@gmail.com> =
wrote:
>>>> Does anyone care that Alias will sometimes be a string, and sometimes =
a number?
>
>> After further review, it appears to me that this change is pretty much
>> required, because otherwise a string like 0xa won't be quoted. =A0I
>> might think it's OK for "123" to turn into 123, but I'm not going to
>> be so happy about "0xa" turning into 10. =A0Please test the attached
>> patch.
>
> I still agree with Dean's original proposal: always quote the values of
> strings.

I'd still rather rip the format out entirely than do that.  Dean's
proposal was based on the idea that it would be safe to quote only the
values and not the keys, which is not something I care to bank on.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Invalid YAML output from EXPLAIN
Next
From: Tom Lane
Date:
Subject: Re: Bad optimizer data for xml (WAS: xml data type implications of no =)