[
https://issues.apache.org/jira/browse/DERBY-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas closed DERBY-4066.
--------------------------------
Resolution: Fixed
This wraps up all of the work which I can think of for this issue. Additional
work needs to be done to improve the memory usage and performance of the LOBs
returned by SQLBlob.getObject() and SQLClob.getObject(). However, that work can
happen as part of DERBY-4754 and/or other issues.
> Allow functions/procedures to take Blob/Clob arguments
> ------------------------------------------------------
>
> Key: DERBY-4066
> URL: https://issues.apache.org/jira/browse/DERBY-4066
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.4.2.0
> Reporter: Rick Hillegas
> Attachments: derby-4066-01-aa-enableLobArgs.diff,
> derby-4066-01-ab-enableLobArgs.diff, derby-4066-01-ag-enableLobArgs.diff,
> derby-4066-01-ak-enableLobArgs.diff, derby-4066-01-al-enableLobArgs.diff,
> derby-4066-02-ac-outputLOBs.diff, derby-4066-03-aa-bigLOBs.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.
