-
- Downloads
Remove zero- and one-argument range constructor functions.
Per discussion, the zero-argument forms aren't really worth the catalog space (just write 'empty' instead). The one-argument forms have some use, but they also have a serious problem with looking too much like functional cast notation; to the point where in many real use-cases, the parser would misinterpret what was wanted. Committing this as a separate patch, with the thought that we might want to revert part or all of it if we can think of some way around the cast ambiguity.
Showing
- doc/src/sgml/rangetypes.sgml 6 additions, 14 deletionsdoc/src/sgml/rangetypes.sgml
- src/backend/commands/typecmds.c 2 additions, 4 deletionssrc/backend/commands/typecmds.c
- src/backend/utils/adt/rangetypes.c 0 additions, 58 deletionssrc/backend/utils/adt/rangetypes.c
- src/include/catalog/catversion.h 1 addition, 1 deletionsrc/include/catalog/catversion.h
- src/include/catalog/pg_proc.h 0 additions, 24 deletionssrc/include/catalog/pg_proc.h
- src/include/utils/rangetypes.h 0 additions, 3 deletionssrc/include/utils/rangetypes.h
- src/test/regress/expected/rangetypes.out 8 additions, 8 deletionssrc/test/regress/expected/rangetypes.out
- src/test/regress/sql/rangetypes.sql 7 additions, 7 deletionssrc/test/regress/sql/rangetypes.sql
Loading
Please register or sign in to comment