You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Anoop Sharma (JIRA)" <ji...@apache.org> on 2016/03/17 17:17:33 UTC

[jira] [Commented] (TRAFODION-1852) Disallow internal system reserved names as user specified columns

    [ https://issues.apache.org/jira/browse/TRAFODION-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199813#comment-15199813 ] 

Anoop Sharma commented on TRAFODION-1852:
-----------------------------------------

cqd traf_allow_reserved_colnames 'ON'
could be used to allow reserved columns.

This is for debugging only and should be used
very carefully and only if really needed by users.
But they need to be aware of that using reserved
names may cause unexpected behavior.

> Disallow internal system reserved names as user specified columns
> -----------------------------------------------------------------
>
>                 Key: TRAFODION-1852
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1852
>             Project: Apache Trafodion
>          Issue Type: Bug
>            Reporter: Anoop Sharma
>            Assignee: Anoop Sharma
>            Priority: Minor
>
> Some column names are reserved for internal trafodion system usage.
> These columns are internally added based on certain conditions
> and have pre-defined types.
> These are:
>   SYSKEY to specify system generated key values if no user primary
>   key has been specified or a store by clause is specified.
>   "_SALT_" to specify salting value for a row.
>   "_DIVISION_*_" to specify computed value for DIVISION BY clause
> Currently, these names are allowed to be used as user specified
> column names and user defined types.
> That prevents certain options to be used (like 'salt by') and can be
> confusing.
> This jira is to disallow user specification of these reserved column 
> names and return an error if they are used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)