[
https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588277#action_12588277
]
Kathey Marsden commented on DERBY-3574:
---------------------------------------
For some reason I had thought it was in README.htm but I guess not.
Here is the wiki page that talks about running the tests.
http://wiki.apache.org/db-derby/DerbyJUnitTesting?highlight=%28JunitTesting%29#head-216e836b20ddca6253e67308abdabb545416232a
When running with the textui runner I usually run with extra memory e.g.
java -XX:MaxPermSize=128M -Xmx512M -Xms512M
-DderbyTesting.oldReleasePath=C:/kmarsden/svnreleases/jars
junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All
> With client, attempting to get the lob length after commit or connection
> close if there was a call to length() before commit does not throw an
> exception
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3574
> URL: https://issues.apache.org/jira/browse/DERBY-3574
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client, Newcomer
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Tiago R. Espinha
> Priority: Trivial
> Attachments: derby3574-wtest.patch, derby3574.patch,
> TestLobLength.java
>
>
> Attempting to get call Blob/Clob.length() after commit or connection close
> does not fail if there was a previous call to length(). If no previous call
> was made an exception is thrown as expected.
> See attached program TestLobLength for repro with commit. If you comment out
> the two lines to get the length before the commit we get the expected
> exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
