| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | 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 16:30:24 |
| Message-ID: | 26510.1276101024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> I'd really like to find a better operator name than ==>. But I'm not
> convinced one exists.
I agree.
> 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.
Perhaps it would be sane to make hstore_in accept either => or ==>, but
not change hstore_out (for now)?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2010-06-09 16:38:53 | Re: Invalid YAML output from EXPLAIN |
| Previous Message | Tom Lane | 2010-06-09 16:25:18 | Re: Invalid YAML output from EXPLAIN |