db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3008) The forCreateTable state of a CreateConstantAction or CreateIndexConstantAction should be a state of the actions, not of the activation.
Date Tue, 14 Aug 2007 21:43:30 GMT
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
            Assignee: Daniel John Debrunner
            Priority: Minor


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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message