db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6923) Passing a ClientClob or ClientBlob from another connection to an INSERT statement results in 'null' being written.
Date Sat, 25 Feb 2017 22:00:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884403#comment-15884403
] 

Bryan Pendleton commented on DERBY-6923:
----------------------------------------

Thanks Gordon. I had the same question about whether 
the cross-server access was relevant, and (independently) I
also tried using just a single Network Server instance and the
behavior did not change for me, either.

However, I *do* notice in the code that the "locator" classes in
the client driver have a member field of type "connection", so
I suspect that the fact that you are using two different *connections*
might be important. Since you have experimented with using a
single server, perhaps you could further experiment with using
a single *connection*?

I am hopeful that somebody else in the Derby development
community who may have more knowledge of the BLOB locator
implementation may be able to offer further suggestions, otherwise
a fair amount of study of the current implementation may be needed.



> Passing a ClientClob or ClientBlob from another connection to an INSERT statement results
in 'null' being written.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6923
>                 URL: https://issues.apache.org/jira/browse/DERBY-6923
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client, Network Server
>    Affects Versions: 10.13.1.1
>         Environment: Java 8
> MacOS
> Windows
>            Reporter: Gordon Innes
>            Priority: Critical
>         Attachments: DerbyEmbeddedOnly.java, DerbyNetworkOnly.java, DerbyNetworkRead.java,
DerbyNetworkWrite.java
>
>
> When assigning a Blob or Clob from a ResultSet to a PreparedStatement parameter on a
second connection, null is written to the column instead.
> Attached the same example using Embedded->Embedded, Embedded->Network, Network->Embedded
and Network->Network.
> Only the Network->Network example exhibits the fault.
> Originally discovered in HA-JDBC's sync code with 2 derby instances on Windows. Example
were tested using MacOS. Both were running on Oracle Java 8 VMs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message