db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-3008) The forCreateTable state of a CreateConstantAction or CreateIndexConstantAction should be a state of the actions, not of the activation.
Date Tue, 02 Oct 2012 04:41:08 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-3008:
-----------------------------------

    Urgency: Normal
     Labels: derby_triage10_10  (was: )
    
> The forCreateTable state of a CreateConstantAction or CreateIndexConstantAction should
be a state of the actions, not of the activation.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3008
>                 URL: https://issues.apache.org/jira/browse/DERBY-3008
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>              Labels: derby_triage10_10
>
> Currently a CreateTableConstantAction sets a state in the activation indicating the activation
is being used for a create table. This state is then subsequently used by CreateConstraintConstantaction
and CreateIndexConstantAction. This state can be known at compile time and is much cleaner
 (self-contained) if it is kept as an attribute of the constant action nodes, rather than
forcing every Activation to have such a field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message