[
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-03-aa-bigLOBs.diff
Attaching derby-4066-03-aa-bigLOBs.diff. This patch adds tests for large (>1M)
LOB inout args. Committed at subversion revision 984916.
As Kristian notes, it would be good to add a test for the case when a LOB is
bigger than the size of VM memory. Right now, that case will fail because
SQLClob.getObject() and SQLBlob.getObject() materialize the LOB contents. I
will add a comment to DERBY-4754 so that we don't forget to add that test case
as we make progress on improving our LOB support.
Touches the following file:
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ParameterMappingTest.java
> 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.
