db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre" <mcintyr...@gmail.com>
Subject Re: DERBY-396: Does it make sense to break this into multiple sub-tasks?
Date Fri, 07 Jul 2006 21:48:46 GMT
On 7/7/06, Bryan Pendleton <bpendleton@amberpoint.com> wrote:
> I'm thinking that it would make sense to break DERBY-396 down into
> multiple sub-tasks. I think this would make it easier to track and
> monitor incremental progress in this area over time.
>
> I am thinking that the following list would be a reasonable set of
> sub-tasks to file.
>
> 1) drop column
> 2) rename column
> 3) change column from null to not null, or vice versa
> 4) change column default value
> 5) change column datatype
>
> Does it sound like a good plan to file 5 JIRA sub-tasks per the above?

Sounds good to me. Each of these items could be working on separately,
they don't necessarily need to be addressed at once.

#3 has already been filed, and is linked into 396 already:

http://issues.apache.org/jira/browse/DERBY-119

#4 was filed, but then closed after fixing the documentation to state
that we don't support setting a new default value.

http://issues.apache.org/jira/browse/DERBY-168

You may just want to open a new issue for that.

andrew

Mime
View raw message