[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12421195 ]
David Heath commented on DERBY-1486:
Please could someone close this bug - I do not appear to have permission myself.
I have created a new bug-report (lower pr
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12421163 ]
David Heath commented on DERBY-1486:
Here is the responce to the communication I had with Lance:
We added wording to hopefully clarify this better in the JDBC
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12421150 ]
Sunitha Kambhampati commented on DERBY-1486:
David Heath (JIRA) wrote:
>
>I appreciate the response of the community and also the communication from
>L
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420992 ]
David Heath commented on DERBY-1486:
I appreciate the response of the community and also the communication from
Lance.
However, I am unsure how to close out this bug, it
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420618 ]
Andreas Korneliussen commented on DERBY-1486:
-
To clarify: this applies only in autocommit:
> Executing a new statement, will cause a commit on the current transact
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420614 ]
Andreas Korneliussen commented on DERBY-1486:
-
Executing a new statement, will cause a commit on the current transaction,
which is in line with the standard. The r
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420608 ]
David Heath commented on DERBY-1486:
Please could someone validate my assumptions from the previous post?
Firstly, from the previous post my understanding is the JDBS stan
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420571 ]
Andreas Korneliussen commented on DERBY-1486:
-
When executing a statement in autocommit mode, the transaction will be
committed.
You are using forward-only, hold
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420470 ]
David Heath commented on DERBY-1486:
I forgot to mention in my previous post that, with auto-commit turned of the
original code ran without Exception, however this is just
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420190 ]
David Heath commented on DERBY-1486:
I have taken a look at the JDBC 3.0 specification and also the JavaDoc and
noticed they did not quite agree on when an auto-commit cau
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12420129 ]
Sunitha Kambhampati commented on DERBY-1486:
I posted a mail to derby-dev earlier, here is the link.
http://www.nabble.com/Re%3A--jira--Commented%3A-%28DERBY-1486%
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12419859 ]
David Heath commented on DERBY-1486:
I just have added close() and flush() to the objStream, re-ran the code and it
does not make a difference - I think the reason it work
I took a quick look at the code, and there is interleaving of resultset
and statements in autocommit mode. Can you try with autocommit off.
I think if readTable1 is called, a commit will be issued for the first
statement in readRows., and then calling getBlob in readRows will
throw the err
(JIRA) [mailto:[EMAIL PROTECTED]
Sent: Friday, July 07, 2006 4:42 PM
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (DERBY-1486) ERROR 40XD0 - When exracting Blob
from a database
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_1241979
4 ]
Daniel John Debrunner
[
http://issues.apache.org/jira/browse/DERBY-1486?page=comments#action_12419794 ]
Daniel John Debrunner commented on DERBY-1486:
--
In your write code you have:
ByteArrayOutputStream byteStream = new ByteArrayOutputStream();
ObjectOutputS
15 matches
Mail list logo
