[
https://issues.apache.org/jira/browse/DERBY-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811596#comment-13811596
]
Rick Hillegas commented on DERBY-6340:
--------------------------------------
Thanks for the new rev of the spec, Dyre. For the record, I'm in favor of the
following choices:
o Don't bother adding the FINAL keyword.
o Don't bother supporting the <cast to distinct> and <cast to source> clauses.
o Allow using builtin type keywords without double quotes when invoking the
implicit coercion functions. E.g.:
SELECT * FROM employees WHERE INTEGER(ssn) > 42;
Thanks,
-Rick
> Add support for CREATE TYPE AS <existing type> (synonym types)
> --------------------------------------------------------------
>
> Key: DERBY-6340
> URL: https://issues.apache.org/jira/browse/DERBY-6340
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Reporter: Dyre Tjeldvoll
> Assignee: Dyre Tjeldvoll
> Attachments: CreateTypeAs_fs_draft.html,
> CreateTypeAs_fs_draft_2.html, CreateTypeAs_fs_draft_3.html,
> CreateTypeAs_fs_draft_3.html
>
>
> The SQL standard (2003) chapter 11.41 <user-defined type definition> allows
> the creation of synonyms or aliases for an existing type: CREATE TYPE AS
> <predefined type>. By allowing this in Derby we would simplify migration
> from, and interoperation with, other databases.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
