Re: deprecating =>, take two
David E. Wheeler <david@kineticode.com>
From: "David E. Wheeler" <david@kineticode.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2010-06-21T16:37:46Z
Lists: pgsql-hackers
On Jun 21, 2010, at 9:20 AM, Robert Haas wrote: > Per that email, and subsequent concurrence, here is a series of > patches which does the following: > > 1. In CVS HEAD, document the hstore(text, text) function and adjust > CREATE OPERATOR to throw a warning when => is used as an operator > name, using the wording previously suggested by Tom. > 2. In the back branches, add an hstore(text, text) function. These > branches already have a tconvert(text, text) function which does the > same thing, but the consensus seemed to be that we do not want to go > back to the name tconvert() for this functionality, and that > back-patching the new name was preferable. > 3. In 8.4 and 8.3, also add hstore(text, text) to the documentation. > 8.2 appears to have no contrib documentation. +1 I was just about to email asking where this was. Glad I checked for new mail first. :-) > Barring vigorous objections, I will apply these tomorrow so that we > can consider deprecating => as an operator name in 9.1, for better > compliance with the SQL standard. So will the CREATE OPERATOR code be updated to issue the warning, rather than just for the case of hstore's => operator? Best, David