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] Updated: (DERBY-3923) Make the datatype optional when declaring columns with generation clauses
Date Fri, 14 Nov 2008 23:26:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rick Hillegas updated DERBY-3923:
---------------------------------

    Attachment: derby-3923-01-ab-optionalDatatype.diff

One test failed: because of the grammar change, db2Compability raises some different errors
than it did before. Attaching derby-3923-01-ab-optionalDatatype.diff, a second rev which changes
the canon for that test. Committed a subversion revision 714186.

> Make the datatype optional when declaring columns with generation clauses
> -------------------------------------------------------------------------
>
>                 Key: DERBY-3923
>                 URL: https://issues.apache.org/jira/browse/DERBY-3923
>             Project: Derby
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3923-01-aa-optionalDatatype.diff, derby-3923-01-ab-optionalDatatype.diff
>
>
> According to the ANSI/ISO spec, the datatype is supposed to be optional for columns defined
by generation clauses. This elegant shorthand is a stretch goal.

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


Mime
View raw message