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

Myrna van Lunteren updated DERBY-3005:
--------------------------------------
    Attachment: DERBY-3005_2.diff
                rrefsqljexternalname.html

Thanks for the review Kim!

Attaching a new patch; I was not pleased with the attempt to describe the use 
of the signatures in the external name as given as a solution to passing SQL 
NULLs to primitive types in the referenced user list thread and FAQ. After some 
thought I decided to just leave that section out, I felt it only looked 
confusing.
I also thought about commenting that although you can specify signatures, you 
still cannot overload a SQL function in Derby (i.e., you cannot use the same 
name for two different functions) but decided against that too, better to 
document what *is* supported.

I did fix up the little issues.
I intend to commit this second patch soon. As always further changes can always 
be made later.

> Document possibility to specify method signature in EXTERNAL NAME when 
> creating a procedure/function
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3005
>                 URL: https://issues.apache.org/jira/browse/DERBY-3005
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.4.1.3
>            Reporter: Kristian Waagan
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-3005.diff, DERBY-3005_2.diff, 
> rrefsqljexternalname.html, rrefsqljexternalname.html
>
>
> In some cases it might be necessary to specify the method signature of the 
> external method used as a function or procedure in Derby (using CREATE 
> FUNCTION or CREATE PROCEDURE).
> This possibility is not documented in the manuals, but there is an entry in 
> the FAQ (http://db.apache.org/derby/faq.html#null_args):
> Either declare the function with RETURNS NULL ON NULL INPUT or define the 
> Java method signature in the external name clause. See the "Create function 
> problem"  derby-user mail list topic.
> The mail thread: 
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200602.mbox/%3c4404e53d.1050...@apache.org%3e
> The relevant sections in the manuals should be updated to describe the 
> feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to