[jira] Resolved: (DERBY-3177) Dropping columns casues auto_increment field to be lost

["Bryan Pendleton (JIRA)" <ji...@apache.org>]

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

Bryan Pendleton resolved DERBY-3177.
------------------------------------

    Resolution: Duplicate

Resolving as a duplicate of DERBY-3175. I agree with Knut's
suggestion that DERBY-3197 describes the other NPE well.
I marked this issue as related to DERBY-3197 since the repro
scripts in this issue might provide some clues about how to
reproduce DERBY-3197.

> Dropping columns casues auto_increment field to be lost
> -------------------------------------------------------
>
>                 Key: DERBY-3177
>                 URL: https://issues.apache.org/jira/browse/DERBY-3177
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.1.4
>         Environment: Windows XP SP2
> JVM: Hotspot JVM 1.6
> Derby: 10.3.1000004.561794
>            Reporter: Charlie Hubbard
>            Assignee: Bryan Pendleton
>         Attachments: bug2.sql, migration-bug.sql
>
>
> I have a DB that I've been updating over time, and I've run into this bug.  After running this script Messages.ID table looses it's auto incrementing column after running the script to completion.  If I create a virgin DB and run this script against the Message table's ID column looses it's auto increment data type.  If you comment out the last three alter table statements the column's auto increment feature is not lost.  You don't have to insert any data into the database for this to happen.
> I tried creating a simpler script to expose this problem, but was unsuccessful.  I tried something like:
> create table Messages ( 
>   Name varchar(256), 
>   KillThis varchar(256),
>   id INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1), 
>   CONSTRAINT MESSAGES_id_pk PRIMARY KEY(id) 
> );
> alter table Messages drop column KillThis;
> However, this DID NOT EXPOSE THE BUG.  So there is something else at work causing this problem.  See the attached script to recreate the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.