[
https://issues.apache.org/jira/browse/DERBY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993589#comment-12993589
]
Rick Hillegas commented on DERBY-268:
-------------------------------------
Hi Eranda,
The idea is that the table element representing the RESTART action should be
added at bind() time, not at parse() time. All that happens at parse() time is
that you mark the AlterTableNode to note that the user has requested RESTART.
The new tableElement should be added at bind() time. At bind() time you will
have access to all of the metadata you need and you should be able to find the
name of the identity column in structures hanging off the TableDescriptor. You
should build the tableElement in AlterTableNode.bind(). See my comment on
2010-11-18 for the processing flow.
Hope this helps,
-Rick
> Add Support for truncate table
> ------------------------------
>
> Key: DERBY-268
> URL: https://issues.apache.org/jira/browse/DERBY-268
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Lance Andersen
> Assignee: Eranda Sooriyabandara
> Priority: Minor
> Attachments: Derby-268.diff, Derby-268.diff,
> TruncateConcurrency.java, TruncateConcurrency.java, TruncateConcurrency.java,
> changes.diff, derby-268-01-ab-enableForInsaneBuilds.diff,
> derby-268-02-aa-permsTest.diff, derby-268-03-aa-npe.diff, tests.diff
>
>
> Adding support for truncate table command will aid to portability
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
