[
https://issues.apache.org/jira/browse/DERBY-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4066:
---------------------------------
Attachment: derby-4066-01-al-enableLobArgs.diff
Attaching a new version of the patch, derby-4066-01-al-enableLobArgs.diff.
Regression tests run cleanly on the previous version now that the initial patch
for DERBY-4754 has been committed.
This new rev adds some additional test cases to verify the following:
1) LOBs can be used as input parameters to procedures, including as ?
parameters.
2) However, you will get a compilation error if you try to declare a procedure
with a LOB output or inout parameter.
If the regression tests pass cleanly, I am inclined to check in this version of
the patch. The next task would then be to make it possible to use LOBs as
output and inout parameters to procedures.
> 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 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.
