[ https://issues.apache.org/jira/browse/DERBY-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512375
]
V.Narayanan commented on DERBY-2932:
------------------------------------
This is because soft upgrade causes the client to switch to the old
behaviour. Since the stored
procedures related to the locator implementation are not present anymore
doing a getBinaryStream
will not return the update sensitive streams. These streams would not
reflect the updates in LOB
after a stream has been got. In both the test cases below the following
sequence of steps is followed.
1) get a new Blob (using con.createBlob())
2) get a InputStream from this Blob
3) write data into the Blob
4) verify that the stream contains this
data.
Since 10.3 onwards due to the presence of the Update sensitive streams
we would get the new data.
However softupgrade and running with a 10.2 server would both result in
the new data not being
reflected in the streams returned.
I have run tests on the attached patch and I did not see any failures.
I request for this patch to be considered for reviews and comments and
if everything is OK a commit
too.
> Connection.createClob() and Connection.createBlob() throw a procedure not found exception
and do not switch to non-locator code upon soft upgrade
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2932
> URL: https://issues.apache.org/jira/browse/DERBY-2932
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.3.0.0, 10.3.1.0, 10.3.1.1
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Priority: Blocker
> Fix For: 10.3.1.2
>
> Attachments: SoftUpgrade_createClob_createBlob_v1.diff, SoftUpgrade_createClob_createBlob_v1.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|