aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/funcs_new.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2015-03-10 10:59:11 -0400
committerRobert Haas <rhaas@postgresql.org>2015-03-10 11:09:41 -0400
commit865f14a2d31af23a05bbf2df04c274629c5d5c4d (patch)
treec9c7e2f919ab55a7c695a572692462f1e6515d8b /src/tutorial/funcs_new.c
parent4f3924d9cd438ba4e6fd639460f8c859c65d45a3 (diff)
downloadpostgresql-865f14a2d31af23a05bbf2df04c274629c5d5c4d.tar.gz
postgresql-865f14a2d31af23a05bbf2df04c274629c5d5c4d.zip
Allow named parameters to be specified using => in addition to :=
SQL has standardized on => as the use of to specify named parameters, and we've wanted for many years to support the same syntax ourselves, but this has been complicated by the possible use of => as an operator name. In PostgreSQL 9.0, we began emitting a warning when an operator named => was defined, and in PostgreSQL 9.2, we stopped shipping a =>(text, text) operator as part of hstore. By the time the next major version of PostgreSQL is released, => will have been deprecated for a full five years, so hopefully there won't be too many people still relying on it. We continue to support := for compatibility with previous PostgreSQL releases. Pavel Stehule, reviewed by Petr Jelinek, with a few documentation tweaks by me.
Diffstat (limited to 'src/tutorial/funcs_new.c')
0 files changed, 0 insertions, 0 deletions