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-4092) You should not be able to invoke a table function as a scalar function
Date Tue, 18 Aug 2009 15:17:14 GMT

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

Rick Hillegas commented on DERBY-4092:
--------------------------------------

Ported 805443 from trunk to 10.5 branch at subversion revision 805444.

> You should not be able to invoke a table function as a scalar function
> ----------------------------------------------------------------------
>
>                 Key: DERBY-4092
>                 URL: https://issues.apache.org/jira/browse/DERBY-4092
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.5.3.1, 10.6.0.0
>
>         Attachments: derby-4092-01-aa-noVTIsAsScalarValues.diff
>
>
> If you invoke a table function as a scalar function, Derby instantiates the ResultSet
returned by the table function and returns that ResultSet. This behavior looks wrong. Derby
should raise an error if you invoke a table function as a scalar function. Here is an example
of the problem:
> ij> values ( badVTI( 'foo' ) );
> 1              
> ---------------
> BadVTI@1ef69   

-- 
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