[DERBY-3008] The forCreateTable state of a CreateConstantAction or CreateIndexConstantAction should be a state of the actions, not of the activation.

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 14/Aug/07 21:42
• Updated: 02/Oct/12 04:40

Description

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.