[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Kathey Marsden updated DERBY-721:
-
Derby Info: [Existing Application Impact, Release Note Needed]
I think this change may affect existing applicaitons. Because of the fact that
the
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Kathey Marsden updated DERBY-721:
-
Fix Version: 10.2.0.0
State of InputStream retrieved from resultset is not clean , if there exists
previous InputStream .
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: DERBY-721_5.patch
Description of patch :
Add master .out file for using DB2 universal driver .
Test :
Execute derbyall with classpath
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Component: JDBC
Network Client
(was: Unknown)
I updated Component/s ...
State of InputStream retrieved from
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: DERBY-721_rollback_1+2.patch
Description of this patch :
This patch rollback DERBY-721.patch and DERBY-721_2.patch .
Test :
Executed
Hello.
Mike Matrigali wrote:
For embedded I was worried about your description of changes, that made
it sound like you somehow were going to buffer the blob in memory. I
see from your changes you basically added reset calls if the underlying
stream was resetable. What I don't know is what
I agree with you conclusion, if in the future someone wants to fix
the network server case then it should not be difficult to make the
embedded case match. Going forward I think our best shot at having
reasonable stream implementations is that we should assume they
can only be read once both on
Hello.
Mike Matrigali wrote:
I am new to this issue and have not reviewed the patch yet. I am just
trying to understand what the correct behavior is. If this has
already been discussed feel free to point that out.I know Sunitha
submitted some fixes in this area, but she will not be able to
Hello Daniel and Mike .
Do you think it is preferable not to allow user to call getStream
twice from one row ,
in order to make a room for releasing memory for cache in ResultSet as
soon as possible ?
Best regards.
Daniel John Debrunner wrote:
Mike Matrigali wrote:
Is there
monologue
Restriction of each row should be read in left-to-right order, and each
column should be read only once in java.sql.ResultSet would have
some impact on Streaming between client and server , because DRDA seems
to stream LOB between client and server only once and in left-to right
order as
I don't have enough information to completely answer, but will
try to state my opinion on the issue.
I think the goals should be:
1) provide same behavior in embedded and network server mode.
2) provide same behavior whether the blob is small or large.
3) optimize the standard case of getting the
I am new to this issue and have not reviewed the patch yet. I am just
trying to understand what the correct behavior is. If this has
already been discussed feel free to point that out.I know Sunitha
submitted some fixes in this area, but she will not be able to look
at these for awhile.
In
Is there anything in the standard that says what the second call to
the get the stream has to do? Imagine the case where the first
stream reads 1 gig of a 2 gig blob, does the second call to
getBinaryStream() have to return the 1st gig again?
Any change that tries to cache the bytes returned
Mike Matrigali wrote:
Is there anything in the standard that says what the second call to
the get the stream has to do? Imagine the case where the first
stream reads 1 gig of a 2 gig blob, does the second call to
getBinaryStream() have to return the 1st gig again?
Yes no.
Nothing in the
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: DERBY-721_3.patch
Description of patch :
I judged that SQLException should not be thrown in
InputStream#close/Reader#close.
I remove
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: DERBY-721_2.patch
Patch for the phenomena found in getCharacterStream
Description:
Modified to reset the source InputStream instead of
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: DERBY-721.patch
Description of the patch:
Modified close method of org.apache.derby.impl.jdbc.BinaryToRawStream to
reset source
[ http://issues.apache.org/jira/browse/DERBY-721?page=all ]
Tomohito Nakayama updated DERBY-721:
Attachment: testLob.java
testResult.txt
These are test program for reproduction of the phenomena what I found , and
result of the
18 matches
Mail list logo
