Skip to content
This repository has been archived by the owner on Jun 7, 2021. It is now read-only.

[TRAFODION-2611] TMUDF with input parameters returns wrong answer #1092

Merged
merged 3 commits into from May 17, 2017
Merged

[TRAFODION-2611] TMUDF with input parameters returns wrong answer #1092

merged 3 commits into from May 17, 2017

Commits on May 11, 2017

  1. [TRAFODION-2612] Internal error in CLEANUP in rare cases. 

    Error in internal SQL issued by CLEANUP caused a piece of memory
to be deallocated twice, resulting in an assertion failure.
    @zellerh
    zellerh committed May 11, 2017
    Configuration menu
    Copy the full SHA
    568c723 View commit details
    Browse the repository at this point in the history

  2. [TRAFODION-2611] TMUDF with input parameters returns wrong answer 

    When a TMUDF had a query with an input parameter or a CURRENT_TIMESTAMP
(or CURRENT_DATE, CURRENT_TIME) in it, we sometimes return incorrect
values.

The problem was that these values were not set up correctly in the
dataflow and they were not shipped as characteristic inputs to the
operators that were referring to them.
    @zellerh
    zellerh committed May 11, 2017
    Configuration menu
    Copy the full SHA
    2a92ad8 View commit details
    Browse the repository at this point in the history

  3. [TRAFODION-2615] TMUDF returns wrong results with small numeric inputs 

    The problem is that the new TINYINT type sometimes is stored in 1
byte, other times in 2 bytes. The TMUDF code makes the assumption that
we can compute the storage size from the precision. The fix is
in the binder and makes sure the storage size matches the storage size
that the TMUDF code will compute.
    @zellerh
    zellerh committed May 11, 2017
    Configuration menu
    Copy the full SHA
    d4677b5 View commit details
    Browse the repository at this point in the history