db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-168) Can't ALTER a column to have a new DEFAULT value.
Date Wed, 09 Mar 2005 04:23:53 GMT
     [ http://issues.apache.org/jira/browse/DERBY-168?page=history ]

Satheesh Bandaram updated DERBY-168:

    Component: Documentation
                   (was: SQL)

I believe the documentation is wrong here...Derby doesn't have the capability to add a default
using ALTER TABLE. We need to fix the documentation.

However, I would suggest filing an Improvement request to add this feature to Derby. I think
Derby could use this enhancement and I would be happy to work with any contributor interested
in trying to put a patch together.

This feature would expose any contributor to each of the parser, query binder and execution
modules but doesn't involve too many changes to each of these. Good improvement to attempt.

> Can't ALTER a column to have a new DEFAULT value.
> -------------------------------------------------
>          Key: DERBY-168
>          URL: http://issues.apache.org/jira/browse/DERBY-168
>      Project: Derby
>         Type: Bug
>   Components: Documentation
>     Versions:
>  Environment: Windows XP SP1 Professional
>     Reporter: George Baklarz
>     Priority: Minor

> Documentation states that an existing column in a table can have a DEFAULT value added
via the ALTER TABLE statement. Unfortunately, none of the syntax provided gives a way of accomplishing
this. An equivalent command from DB2 would be:
> Is this an error in the documentation, and omission in the product, or is there a different
command to accomplish this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message