[
https://issues.apache.org/jira/browse/DERBY-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675410#action_12675410
]
Kathey Marsden commented on DERBY-4066:
---------------------------------------
Bryan said.
>Perhaps it was one of those cases where the functionality was disabled
>to preserve compatibility with an older version of DB2?
Perhaps that is the case, but it is not entirely clear from the history. The
exception was added before we had CREATE FUNCTION and CREATE PROCEDURE syntax,
so there never were tests for that so it good Rick is adding it.
On the patch, I think it would be good to enable this test for client to make
sure lob parameters are working properly there too.
> Allow functions/procedures to take Blob/Clob arguments
> ------------------------------------------------------
>
> Key: DERBY-4066
> URL: https://issues.apache.org/jira/browse/DERBY-4066
> Project: Derby
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 10.4.2.0
> Reporter: Rick Hillegas
> Attachments: derby-4066-01-aa-enableLobArgs.diff
>
>
> Derby objects if you try to declare a function or procedure with an argument
> whose type is BLOB or CLOB. These kinds of arguments are allowed in the SQL
> standard and the matching Java types are java.sql.Blob and java.sql.Clob. See
> the SignatureMatching.html summary attached to DERBY-3652.
> We should lift this restriction and allow functions and procedures to take
> large object arguments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
