-
- Downloads
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.
Showing
- doc/src/sgml/func.sgml 1 addition, 1 deletiondoc/src/sgml/func.sgml
- doc/src/sgml/syntax.sgml 16 additions, 5 deletionsdoc/src/sgml/syntax.sgml
- doc/src/sgml/xfunc.sgml 3 additions, 3 deletionsdoc/src/sgml/xfunc.sgml
- src/backend/commands/operatorcmds.c 0 additions, 10 deletionssrc/backend/commands/operatorcmds.c
- src/backend/parser/gram.y 10 additions, 1 deletionsrc/backend/parser/gram.y
- src/backend/parser/scan.l 6 additions, 0 deletionssrc/backend/parser/scan.l
- src/test/regress/expected/create_operator.out 4 additions, 3 deletionssrc/test/regress/expected/create_operator.out
- src/test/regress/expected/polymorphism.out 67 additions, 0 deletionssrc/test/regress/expected/polymorphism.out
- src/test/regress/sql/create_operator.sql 1 addition, 1 deletionsrc/test/regress/sql/create_operator.sql
- src/test/regress/sql/polymorphism.sql 16 additions, 0 deletionssrc/test/regress/sql/polymorphism.sql
Loading
Please register or sign in to comment