db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3922) Enable the adding of generated columns via ALTER TABLE
Date Tue, 18 Nov 2008 19:37:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648720#action_12648720

Dag H. Wanvik commented on DERBY-3922:

Looked at this patch, it looks good to me! Verified that bugs mentioned
appear in the bind phase of UpdateNode when running the test unless fixed
as in this patch.

> Enable the adding of generated columns via ALTER TABLE
> ------------------------------------------------------
>                 Key: DERBY-3922
>                 URL: https://issues.apache.org/jira/browse/DERBY-3922
>             Project: Derby
>          Issue Type: Task
>          Components: SQL
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3922-01-aa-repopulate.diff
> The initial grammar patch for generated columns did not include ALTER TABLE support.
This support cannot be added until we check in the UPDATE logic for generated columns. Adding
a generated column to an existing table is supposed to calculate the generated column's values
for all rows currently in the table.

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

View raw message