[
https://issues.apache.org/jira/browse/DERBY-6843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030124#comment-15030124
]
Anjana commented on DERBY-6843:
-------------------------------
Hi Rick,
Thanks for follow-up. However adding CHECK NOT NULL constraint also did not
help importing identity column value into column that has identity type as
"GENERATED ALWAYS".
Thanks,
Anjana.
> Altering the Identity columns rules
> ------------------------------------
>
> Key: DERBY-6843
> URL: https://issues.apache.org/jira/browse/DERBY-6843
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.11.1.1, 10.12.1.1
> Environment: CENTOS
> Reporter: Anjana
>
> We do export of from one derby database to another. Our database defined
> identity type as ''GENERATED ALWAYS" Due to which the import does not
> consider the identity column value from the export file.
> Our requirement is to import those identity column values as well.
> As per understanding one of the option in derby is to create table with
> identity type as "GENERATED BY DEFAULT" . However need to understand if there
> is alternative in derby where in we can modify the identity type before
> import to ''GENERATED by DEFAULT" and then after import is successfully
> change it back to "GENERATED ALWAYS".
> Appreciate if any one can guide on same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
