[
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-ak-enableLobArgs.diff
Attaching derby-4066-01-ak-enableLobArgs.diff. This is a re-warmed version of
the patch.
In addition to bringing the patch up to date with the current state of the
trunk, this patch adds some new test cases to verify the setting of LOB
function args using ? parameters. These new tests fail, so the patch is not
ready for commit.
Also, more tests are needed to examine the behavior of procedure arguments. As
currently coded, the patch should still forbid the declaration of LOB output
procedure arguments.
I believe that the problem with ? CLOB args is backed up behind DERBY-4754.
> 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 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.
