db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6390) Document the WHEN clause in the CREATE TRIGGER statement
Date Wed, 30 Oct 2013 18:21:35 GMT

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

Kim Haase commented on DERBY-6390:

I noticed that length discrepancy when I ran a command line Rick suggested a while back to
get the data type values. Currently the only columns for which we document the length as Integer.MAX_VALUE
are the ones where the data type is not part of the public API (like REFERENCEDCOLUMNS). Anything
we document as LONG VARCHAR is shown with 32,700 as the maximum length. So we should probably
continue in that practice.

> Document the WHEN clause in the CREATE TRIGGER statement
> --------------------------------------------------------
>                 Key: DERBY-6390
>                 URL: https://issues.apache.org/jira/browse/DERBY-6390
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>         Attachments: DERBY-6390.diff, DERBY-6390.stat, DERBY-6390.zip
> The documentation should be updated with information about the WHEN clause that was added
to the CREATE TRIGGER statement in DERBY-534. The functional specification attached to that
issue has a list of topics that need updating.

This message was sent by Atlassian JIRA

View raw message