[ http://issues.apache.org/jira/browse/DERBY-167?page=all ]
Tomohito Nakayama resolved DERBY-167:
-------------------------------------
Resolution: Fixed
Solution 1 in this issue was done.
> Inserting values in an identity column
> --------------------------------------
>
> Key: DERBY-167
> URL: http://issues.apache.org/jira/browse/DERBY-167
> Project: Derby
> Type: Improvement
> Components: SQL
> Versions: 10.1.1.0
> Environment: SQL
> Reporter: Christian Rodriguez
> Assignee: Tomohito Nakayama
> Attachments: DERBY-167_7.patch
>
> It is not possible to insert a specific value in a column defined as
> identity. This makes it very hard to migrate from other RDBMSs or to import
> data dumped from other databases.
> For example, an autoincrement column in MySQL should be an identity column.
> The problem is that when the data is dumped from MySQL to a file, it
> generates inserts with values. These values cant be inserted in the Derby
> table.
> Posible solutions: 1. being able to "generate by default as identity" 2.
> being able to disable the "identity" feature for a column 3. being able to
> generate a column as non identity and after data is populated, alter table to
> add the "identity" to the column.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
