-
- Downloads
Adjust collation determination rules as per discussion.
Remove crude hack that tried to propagate collation through a function-returning-record, ie, from the function's arguments to individual fields selected from its result record. That is just plain inconsistent, because the function result is composite and cannot have a collation; and there's no hope of making this kind of action-at-a-distance work consistently. Adjust regression test cases that expected this to happen. Meanwhile, the behavior of casting to a domain with a declared collation stays the same as it was, since that seemed to be the consensus.
Showing
- src/backend/parser/parse_collate.c 5 additions, 22 deletionssrc/backend/parser/parse_collate.c
- src/backend/parser/parse_func.c 1 addition, 1 deletionsrc/backend/parser/parse_func.c
- src/backend/parser/parse_target.c 1 addition, 1 deletionsrc/backend/parser/parse_target.c
- src/test/regress/expected/collate.linux.utf8.out 27 additions, 27 deletionssrc/test/regress/expected/collate.linux.utf8.out
- src/test/regress/expected/collate.out 16 additions, 16 deletionssrc/test/regress/expected/collate.out
- src/test/regress/sql/collate.linux.utf8.sql 5 additions, 5 deletionssrc/test/regress/sql/collate.linux.utf8.sql
- src/test/regress/sql/collate.sql 4 additions, 4 deletionssrc/test/regress/sql/collate.sql
Loading
Please register or sign in to comment