Andrew Gierth <and...@tao11.riddles.org.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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
