[
https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Stroffek updated DERBY-2953:
---
Fix Version/s: (was: 10.4.0.0)
I removed fix-version info.
Dump the information about
[
https://issues.apache.org/jira/browse/DERBY-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dyre Tjeldvoll updated DERBY-3528:
--
Fix Version/s: 10.4.0.0
This issue has no fix version, but has been checked in to trunk after
[Auto-generated mail]
*tinderbox_trunk16* 641764/2008-03-27 11:02:27 CET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0274274 086.96% derbyall
F:1,E:096949693 0
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
[
https://issues.apache.org/jira/browse/DERBY-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582763#action_12582763
]
Kathey Marsden commented on DERBY-2892:
---
I was looking at improving the error
Yes, it was an EG decision to correct the javadocs for setFetchSize()
as if there is no limit specified via setMaxRows(), getMaxRows()
returns 0 thus using:
0 = |rows| = |this.getMaxRows()|
can be problematic depending on implementations.
Also setFetchSize is a hint and can be ignored
Bryan Pendleton [EMAIL PROTECTED] writes:
I propose that Thomas Nielsen shall be a Derby committer.
+1
Dag
