[
https://issues.apache.org/jira/browse/DERBY-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677331#action_12677331
]
Kristian Waagan commented on DERBY-4066:
----------------------------------------
I looked at derby-4066-01-ab-enableLobArgs.diff, and except for an occurrence
of inconsistent use of tabs/spaces (CreateAliasNode), I didn't find anything
more to comment on.
What I would like to see, are tests testing larger LOBs used as arguments. I
think objects larger than what can be sent as a single message in DRDA and
larger than the JVM heap would be good candidates.
We already have a test for the low memory scenario (see tests.memory._Suite),
maybe a new test can be added there. Of course, such a test must not explicitly
materialize the LOB.
> 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-4066-01-ab-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.
