Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

parse_target.c

  • Tom Lane's avatar
    a19002d4
    Adjust collation determination rules as per discussion. · a19002d4
    Tom Lane authored
    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.
    a19002d4
    History
    Adjust collation determination rules as per discussion.
    Tom Lane authored
    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.