You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Uriah Eisenstein <ur...@gmail.com> on 2010/08/28 18:07:25 UTC
Bug: RENAME COLUMN on a column GENERATED ALWAYS AS IDENTITY removes
the auto-increment property
Hi,
I hope this is the place to post such issues. I've recently renamed an
identity column, and then found that it no longer functioned as one; the
next row inserted into the table got the value 0 in this column, and further
rows could not be inserted without setting the column value manually (due to
the unique or primary key constraint which still remained on it).
I didn't see anything in the documentation about this; I suppose renaming an
identity column should either be forbidden or keep it being an identity
column.
I'm using Apache Derby 10.6.1.0 (embedded driver) on Windows XP SP3 with JRE
1.6.0.21.
Thanks,
Uriah Eisenstein
Re: Bug: RENAME COLUMN on a column GENERATED ALWAYS AS IDENTITY
removes the auto-increment property
Posted by Uriah Eisenstein <ur...@gmail.com>.
Argh, sorry. I usually search for existing bugs before submitting a new one,
but sometimes forget... This is indeed the issue. Thanks!
On Sat, Aug 28, 2010 at 6:15 PM, Bryan Pendleton <bpendleton.derby@gmail.com
> wrote:
> I hope this is the place to post such issues. I've recently renamed an
>> identity column, and then found that it no longer functioned as one;
>>
>
> That's DERBY-4693, I believe:
> https://issues.apache.org/jira/browse/DERBY-4693
>
> It's fixed in the 10.6 branch, so you could build the fix for your own use.
>
> There's also a 10.6 patch release in the works for the fall:
> http://wiki.apache.org/db-derby/DerbyTenSixTwoRelease
>
> thanks,
>
> bryan
>
Re: Bug: RENAME COLUMN on a column GENERATED ALWAYS AS IDENTITY removes
the auto-increment property
Posted by Bryan Pendleton <bp...@gmail.com>.
> I hope this is the place to post such issues. I've recently renamed an
> identity column, and then found that it no longer functioned as one;
That's DERBY-4693, I believe: https://issues.apache.org/jira/browse/DERBY-4693
It's fixed in the 10.6 branch, so you could build the fix for your own use.
There's also a 10.6 patch release in the works for the fall:
http://wiki.apache.org/db-derby/DerbyTenSixTwoRelease
thanks,
bryan