>>>>> "Tom" == Tom Lane <t...@sss.pgh.pa.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) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
