Re: hstore parser incorrectly handles malformed input

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: hstore parser incorrectly handles malformed input
Дата
Msg-id 19559.1335536531@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: hstore parser incorrectly handles malformed input  (Ryan Kelly <rpkelly22@gmail.com>)
Ответы Re: hstore parser incorrectly handles malformed input  (Ryan Kelly <rpkelly22@gmail.com>)
Список pgsql-bugs
Ryan Kelly <rpkelly22@gmail.com> writes:
> As long as we make it consistent on both sides of the '=>' (and document
> it, too), then I don't really care either way. Currently you have to use
> quotes to get an empty key, so I thought it natural to that you should
> have to quote to get an empty value.

> I've attached a modified version of Tom's patch which also allows empty
> keys.

Hm ... I don't agree that keys and values are interchangeable, and
I don't see that empty keys are a good thing (whereas empty values are
clearly a reasonable edge case).  So I think this is going a bit far;
it seems to me it'd be giving up a lot of syntax-error detection
capability in return for some not-actually-helpful symmetry.

On the other hand, I seldom use hstore so I'm probably not the best
person to be judging the appropriateness of these options.  Any other
votes out there?

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: BUG #6619: Misleading output from slave when host is not running
Следующее
От: sathish@myc2s.com
Дата:
Сообщение: BUG #6620: Out of memory error