| Key: |
DERBY-25
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Tulika Agrawal
|
| Votes: |
1
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
05/May/05 07:35 AM
|
|
Reporting for Mamta Satoor.
If we use insert into desttable, select
distinct from source, into a desttable which has autoincrement
column in it, we might see gaps in the autoincrement column if
there are duplicated rows in the source table. The reason for
this is Derby projects values into destination table columns before
building a distinct resultset from the source table. The piece
of code doing this is in org.apache.derby.impl.sql.execute.ProjectRestrictResultSet class's getNextRowCore() method where it calls doProjection.
|
|
Description
|
Reporting for Mamta Satoor.
If we use insert into desttable, select
distinct from source, into a desttable which has autoincrement
column in it, we might see gaps in the autoincrement column if
there are duplicated rows in the source table. The reason for
this is Derby projects values into destination table columns before
building a distinct resultset from the source table. The piece
of code doing this is in org.apache.derby.impl.sql.execute.ProjectRestrictResultSet class's getNextRowCore() method where it calls doProjection.
|
Show » |
| No work has yet been logged on this issue.
|
|
INSERT INTO SELECT DISTINCT ... skips some values for autoincrement column
