db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3959) Reference Manual needs information on generated columns
Date Wed, 07 Jan 2009 21:48:46 GMT

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

Rick Hillegas commented on DERBY-3959:

Thanks for the patch, Kim. Looks good. Some comments follow:

Two typos:

  "Column definition" section: "if" should be capitalized.

  1st paragraph: "if" should be capitalized.

Substantive issue:

Both rrefsqlj30540 and rrefsqljrevoke say that a table will be dropped if one of its generation
clauses depends on a role-based EXECUTE privilege which is subsquently dropped. The functional
spec says that this is the expected behavior but subsequent discussion on DERBY-481 has failed
to find good motivation for this harsh behavior and, in fact, this is not how Derby behaves
right now. A little more discussion may happen related to this issue on DERBY-3949. However,
I suspect that I will end up removing this harsh assertion from the functional spec and we
should therefore remove this from the user documentation too.


> Reference Manual needs information on generated columns
> -------------------------------------------------------
>                 Key: DERBY-3959
>                 URL: https://issues.apache.org/jira/browse/DERBY-3959
>             Project: Derby
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-3959.diff, DERBY-3959.stat, DERBY-3959.zip
> The Generated Columns specification attached to DERBY-481 describes changes that need
to be made to the Derby Reference Manual to document this new feature. This issue covers the
implementation of these changes.

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

View raw message