[
https://issues.apache.org/jira/browse/DERBY-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-268:
---------------------------------
knut, that sounds like a good approach. or at least sharing more code in the
same file - i would trust the existing code from working features more than the
truncate code. truncate and compress should be able to share all the code
that does the new conglomerate stuff, and just skip the load part. It does
share some code which is why it does not have the compress bug. Eventually
truncate might have more specific code if we implement the other syntax.
I've been trying to think of what might be missing. Are there any tests for
truncate table with sql roles/permissions. It may have been added after
truncate code was added.
> 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-01-ab-enableForInsaneBuilds.diff,
> Derby-268.diff, tests.diff
>
>
> Adding support for truncate table command will aid to portability
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
