You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/01/12 20:14:46 UTC

[jira] Updated: (DERBY-4469) Fix the CASTing behavior of UDTs

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

Kathey Marsden updated DERBY-4469:
----------------------------------

    Fix Version/s: 10.6.1.0

> Fix the CASTing behavior of UDTs
> --------------------------------
>
>                 Key: DERBY-4469
>                 URL: https://issues.apache.org/jira/browse/DERBY-4469
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.1.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.6.1.0
>
>         Attachments: derby-4469-01-aa-castNullsAndUntypedParameters.diff, derby-4469-02-ab-illegalCasts.diff
>
>
> The actual behavior of UDTs, now under construction, does not conform to the spec. The spec says that you can't CAST to or from UDTs. This is probably too harsh. We should allow the following CAST
>   cast ( null as udtType )
> I also think that we should allow at least the implicit casting of subtypes to supertypes since Java gives us the ability to discover the type graph. See Knut's comment on DERBY-651 on Dec 11, 2009.

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