[
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-ab-enableLobArgs.diff
Thanks for the quick feedback, Bryan and Kathey. Attaching a second rev of the
patch: derby-4066-01-ab-enableLobArgs.diff. This changes the canon for the LOB
test, which used to expect the old failure. I also incorporated Kathey's
recommendation to change the test to run client/server as well as embedded.
This turned up another problem: in the client/server configuration the
numeric/decimal tests in AnsiSignaturesTest raise an overflow condition. I
think this is a bug and I will log an issue to track it. In the meantime, I
have disabled those tests for the client/server configuration.
In addition, the XMLTypeAndOpsTest had errors because the original patch
allowed XML datatypes as method parameters too. That situation should still be
forbidden until we provide an implementation of JDBC's SQLXML datatype. This
second patch disallows XML datatypes as method parameters.
Touches the following additional files:
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/LOB.sql
M java/testing/org/apache/derbyTesting/functionTests/master/LOB.out
I will run the regression tests again.
> 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.
