[jira] Updated: (DERBY-3) Identity column not filled consecutively with "insert ... select distinct"

["Satheesh Bandaram (JIRA)" <de...@db.apache.org>]

     [ http://issues.apache.org/jira/browse/DERBY-3?page=all ]

Satheesh Bandaram updated DERBY-3:
----------------------------------

    Component: SQL

While it may be desirable not to have gaps in identity values, the current implementation does match required uniqueness.

> Identity column not filled consecutively with "insert ... select distinct"
> --------------------------------------------------------------------------
>
>          Key: DERBY-3
>          URL: http://issues.apache.org/jira/browse/DERBY-3
>      Project: Derby
>         Type: Bug
>   Components: SQL
>  Environment: Derby Snapshot svnversion 46005
> or Cloudscape 10.0 GA
>     Reporter: Christian d'Heureuse

>
> When an "insert ... select distinct" is used to fill a table with an identity column, gaps occur in the identity column. The caps correspond to the rows of the source table that have been suppressed with "distinct".
> Example:
> create table temp1 (
>    s varchar(10));
> insert into temp1 values 'a','a','a','b','c','c','c','d';
> create table temp2 (
>    i integer not null
>       generated always as identity
>       primary key,
>    s varchar(10));
> insert into temp2 (s)
>    select distinct s from temp1;
> select * from temp2;
> output:
>  1   a
>  4   b
>  5   c
>  8   d

-- 
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