| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane), robertmhaas(at)gmail(dot)com (Robert Haas), Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: hstore ==> and deprecate => |
| Date: | 2010-06-09 18:29:47 |
| Message-ID: | 87bpbkrrgg.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> While I don't like the inconsistency between ==> or whatever and
>> the use of => in type input and output, I regard the text
>> representation as being much harder to change safely, since client
>> code will be parsing it. In this case the inconsistency seems like
>> a much smaller problem than changing the text representation.
Tom> Perhaps it would be sane to make hstore_in accept either => or
Tom> ==>, but not change hstore_out (for now)?
I'd be happy with that.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-09 18:50:23 | Re: Invalid YAML output from EXPLAIN |
| Previous Message | Carsten Kropf | 2010-06-09 18:28:53 | Re: Custom index structure and strange count problem |