[ https://issues.apache.org/jira/browse/DERBY-6882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234341#comment-15234341 ]
Rick Hillegas commented on DERBY-6882: -------------------------------------- Hi Alexsei, I will port this enhancement to the 10.12 branch if you still need it. But I won't bother if you have already found an adequate workaround for your problem. Please let me know. Thanks. > Add functionality to ALTER TABLE: switch from GENERATED ALWAYS to GENERATED > BY DEFAULT > -------------------------------------------------------------------------------------- > > Key: DERBY-6882 > URL: https://issues.apache.org/jira/browse/DERBY-6882 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.12.1.1 > Reporter: Aleksei Kovura > Assignee: Rick Hillegas > Labels: features > Attachments: derby-6882-01-aa-initialCode.diff, > derby-6882-01-bb-withTests.diff > > > I'm trying to import data from another Derby database with foreignViews tool > because system tables got corrupted somehow (see > https://issues.apache.org/jira/browse/DERBY-6876). Tables contain generated > ID columns (created as "GENERATED ALWAYS"). Importing data and allowing Derby > to generate new IDs in generated columns will break relationships between > tables (old tables have counter gaps there due to deletes - IDs won't match). > For a clean import without breaking DDL information in DB version control I > would like to be able to switch between generated types as follows: > > ALTER TABLE table1 ALTER COLUMN col1 SET GENERATED BY DEFAULT [ AS IDENTITY] > ALTER TABLE table1 ALTER COLUMN col1 SET GENERATED ALWAYS [ AS IDENTITY] -- This message was sent by Atlassian JIRA (v6.3.4#6332)