[
https://issues.apache.org/jira/browse/DERBY-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik reassigned DERBY-6089:
Assignee: Rick Hillegas
CallableStatement#registerOutParameter on client lacks check
[
https://issues.apache.org/jira/browse/DERBY-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik reassigned DERBY-6088:
Assignee: Rick Hillegas
PreparedStatementTest42 lacks fail call when operation
[
https://issues.apache.org/jira/browse/DERBY-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588140#comment-13588140
]
Dag H. Wanvik commented on DERBY-6088:
--
I guess this is one is addressed by your
[
https://issues.apache.org/jira/browse/DERBY-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6017:
--
Attachment: d6017-3a-weme-test-failure.diff
Attaching d6017-3a-weme-test-failure.diff
Java DB testing and reporting infrastructure.
Success nightly trunk (rev 1450363)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5573326-report/
[
https://issues.apache.org/jira/browse/DERBY-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588221#comment-13588221
]
Knut Anders Hatlen commented on DERBY-6076:
---
I logged on to cms.apache.org and
[
https://issues.apache.org/jira/browse/DERBY-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588229#comment-13588229
]
Knut Anders Hatlen commented on DERBY-6076:
---
Hmm... No, the previous commit
[
https://issues.apache.org/jira/browse/DERBY-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas resolved DERBY-6088.
--
Resolution: Fixed
Fix Version/s: 10.10.0.0
Hi Dag,
Yes, this bug should be fixed by
Java DB testing and reporting infrastructure.
Success continuous trunk (rev 1450695)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5573337-report/
[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6000:
-
Attachment: derby-6000-20-aa-negativeUpdateObject.diff
Attaching
Rick Hillegas created DERBY-6094:
Summary: Derby ignores DriverManager.setLoginTimeout()
Key: DERBY-6094
URL: https://issues.apache.org/jira/browse/DERBY-6094
Project: Derby
Issue Type: Bug
[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6094:
-
Attachment: LoginTimeoutTest.java
Attaching LoginTimeoutTest, a program which shows this
[
https://issues.apache.org/jira/browse/DERBY-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588433#comment-13588433
]
Bryan Pendleton commented on DERBY-6076:
The icons show up for me, too. Thanks!
Java DB testing and reporting infrastructure.
Error continuous trunk (rev 1450776)
50 errors.
Test report: http://download.java.net/javadesktop/derby/javadb-5573340-report/
[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588550#comment-13588550
]
Rick Hillegas commented on DERBY-6094:
--
In private email, JDBC spec lead Lance
[
https://issues.apache.org/jira/browse/DERBY-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-6076.
---
Resolution: Fixed
Fix Version/s: 10.10.0.0
Assignee: Knut Anders
[
https://issues.apache.org/jira/browse/DERBY-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588052#comment-13588052
]
Mamta A. Satoor edited comment on DERBY-6045 at 2/27/13 8:29 PM:
I was wondering what is the default maximum memory for hash joins.
Looking at OptimizerFactoryImpl I see
protected int maxMemoryPerTable = 1048576 unless overridden by
derby.language.maxMemoryPerTable;
Is actually intended per table or per active query? I don't see the
property in the
Hi,
I was wondering if there was a way to dump all the plans considered by
the optimizer. I realize that it can be a huge output since optimizer
can be going through many different plan options but it will be a good
information to have when looking at why one plan was picked over the
other. I am
[
https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1353#comment-1353
]
Mamta A. Satoor commented on DERBY-6053:
Backported changes to 10.9 codeline with
[
https://issues.apache.org/jira/browse/DERBY-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor reopened DERBY-6053:
reopening the issue for backporting
Client should use a prepared statement
Hi,
I noticed that the version of 10.9 on the 10.9 branch is currently
10.9.2.2, but there was no such version in JIRA.
So I added it.
However, I'm not sure this was the right thing to do, because there
are these versions now:
10.9.2.2 Head of 10.9 branch after abortive 10.9.2 rc2
10.9.2.1 Head
Java DB testing and reporting infrastructure.
Error nightly trunk (rev 1450776)
2 errors.
Test report: http://download.java.net/javadesktop/derby/javadb-5573354-report/
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13589286#comment-13589286
]
Myrna van Lunteren commented on DERBY-5977:
---
forgot to mention; these changes
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5977:
--
Attachment: DERBY-5977_3.diff
DERBY-5977_3.stat
Attaching a patch
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13589286#comment-13589286
]
Myrna van Lunteren edited comment on DERBY-5977 at 2/28/13 7:29 AM:
26 matches
Mail list logo
