trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From selvaganesang <>
Subject [GitHub] incubator-trafodion pull request: [TRAFODION-1887] Upsert into ali...
Date Tue, 15 Mar 2016 20:20:22 GMT
Github user selvaganesang commented on a diff in the pull request:
    --- Diff: core/sql/optimizer/BindRelExpr.cpp ---
    @@ -10171,17 +10164,26 @@ matched clause of merge). If the upsert caused a row to be updated
in the
     base table then the old version of the row will have to be deleted from 
     indexes, and a new version inserted. Upsert is being transformed to merge
     so that we can delete the old version of an updated row from the index.
    +Upsert is also converted into merge when there are omitted cols with default values and

    +TRAF_UPSERT_WITH_INSERT_DEFAULT_SEMANTICS is set to  OFF in case of aligned format table
    +omitted current timestamp cols in case of non-aligned row format
    --- End diff --
    For upsert, in case of non-aligned format, if any column other than the columns with default
current is omitted, the default value is resolved at the time of select. If the current default
column is omitted it will be always changed to merge. User can't force a different behavior
for non-aligned format in this specific case. Rationale here: If we allow user to control
it, then all omitted default columns should always be populated at the time of upsert for
the merge to work correctly.
    For non-aligned format, user control it using the above cqd. Default behavior is change
it to merge if the default columns are omitted in upsert.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message