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

nodeValuesscan.c

Blame
    • Tom Lane's avatar
      398f70ec
      Preserve column names in the execution-time tupledesc for a RowExpr. · 398f70ec
      Tom Lane authored
      The hstore and json datatypes both have record-conversion functions that
      pay attention to column names in the composite values they're handed.
      We used to not worry about inserting correct field names into tuple
      descriptors generated at runtime, but given these examples it seems
      useful to do so.  Observe the nicer-looking results in the regression
      tests whose results changed.
      
      catversion bump because there is a subtle change in requirements for stored
      rule parsetrees: RowExprs from ROW() constructs now have to include field
      names.
      
      Andrew Dunstan and Tom Lane
      398f70ec
      History
      Preserve column names in the execution-time tupledesc for a RowExpr.
      Tom Lane authored
      The hstore and json datatypes both have record-conversion functions that
      pay attention to column names in the composite values they're handed.
      We used to not worry about inserting correct field names into tuple
      descriptors generated at runtime, but given these examples it seems
      useful to do so.  Observe the nicer-looking results in the regression
      tests whose results changed.
      
      catversion bump because there is a subtle change in requirements for stored
      rule parsetrees: RowExprs from ROW() constructs now have to include field
      names.
      
      Andrew Dunstan and Tom Lane
    nodeValuesscan.c 8.54 KiB