[
https://issues.apache.org/jira/browse/DERBY-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4754:
---------------------------------
Attachment: derby-4066-02-ac-outputLOBs.diff
Attaching derby-4066-02-ac-outputLOBs.diff. This patch allows LOB-valued
OUT/INOUT arguments to Derby routines. Regression tests passed cleanly for me.
As follow-on work, we will want to verify that large LOBs behave correctly.
Hopefully, the work on DERBY-4544 will be applicable to DERBY-4754 and help
improve the performance of LOB arguments.
Touches the following files:
--------------
M java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
Allow LOB types as OUT and INOUT arguments in routine declarations.
--------------
M java/engine/org/apache/derby/impl/jdbc/EmbedCallableStatement.java
Retrieve LOB values from OUT and INOUT parameters of CallableStatements.
--------------
M java/client/org/apache/derby/client/net/NetCursor.java
M java/drda/org/apache/derby/impl/drda/EXTDTAInputStream.java
M java/drda/org/apache/derby/impl/drda/DRDAResultSet.java
M java/drda/org/apache/derby/impl/drda/DRDAConnThread.java
Transport LOB-valued OUT/INOUT parameters across the network.
--------------
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ParameterMappingTest.java
Verify small LOB-valued OUT/INOUT arguments.
> SQLClob.getObject() should always return a java.sql.Clob
> --------------------------------------------------------
>
> Key: DERBY-4754
> URL: https://issues.apache.org/jira/browse/DERBY-4754
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.6.1.0
> Reporter: Rick Hillegas
> Attachments: derby-4066-02-ac-outputLOBs.diff,
> derby-4754-01-aa-harmonyLOBs.diff, derby-4754-01-ab-harmonyLOBs.diff
>
>
> Depending on what SQLClob wraps (a string, a stream, a java.sql.Clob),
> SQLClob.getObject() sometimes returns a string and other times returns a
> java.sql.Clob. In at least one spot, the compiler expects that
> SQLClob.getObject() will always return a java.sql.Clob. See the final cast
> compiled by SQLToJavaValueNode.generateJavaValue(). I believe that the
> compiler is correct and SQLClob.getObject() should behave predictably.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
