You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2020/07/09 12:41:00 UTC

[jira] [Reopened] (DERBY-7084) Identity column data import does not increment generator

     [ https://issues.apache.org/jira/browse/DERBY-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard N. Hillegas reopened DERBY-7084:
----------------------------------------
    Bug behavior facts: Seen in production

Re-opening this issue. It would be helpful to add a note to the SYSCS_UTIL.SYSCS_IMPORT_TABLE() documentation and give Bryan's workaround.

> Identity column data import does not increment generator
> --------------------------------------------------------
>
>                 Key: DERBY-7084
>                 URL: https://issues.apache.org/jira/browse/DERBY-7084
>             Project: Derby
>          Issue Type: Bug
>            Reporter: Makkus B.
>            Priority: Major
>
> When importing table data containing identity column vales (defined as GENERATED BY DEFAULT AS IDENTITY) via SYSCS_IMPORT_DATA (or SYSCS_IMPORT_TABLE)  the data will be imported (when identity column was defined as GENERATED BY DEFAULT AS IDENTITY) , but the (internal) table index generator will not be updated. If the column is further defined as UNIQUE (or PRIMARY KEY) new data might not be added to the table (if the internal index will match an imported one).
> The expected behaviour would be that the internal index would always stay ahead of identity values inserted to the table. This is: for a new table the index defaults to 1. If data is imported to a new table, the index should not stay at 1 but become 1+max(imported_index). So the table can be continued to be used after the import.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)