[
https://issues.apache.org/jira/browse/DERBY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094465#comment-13094465
]
Knut Anders Hatlen commented on DERBY-5359:
---
Thanks for the patch, Jayaram!
I
[
https://issues.apache.org/jira/browse/DERBY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5359:
--
Issue fix info: (was: [Patch Available])
The changes in lib/index.html look fine,
[
https://issues.apache.org/jira/browse/DERBY-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094507#comment-13094507
]
Kristian Waagan commented on DERBY-5283:
I think we can improve the situation
[
https://issues.apache.org/jira/browse/DERBY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094511#comment-13094511
]
Knut Anders Hatlen commented on DERBY-5359:
---
I found a good explanation here:
[
https://issues.apache.org/jira/browse/DERBY-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-5396.
---
Resolution: Fixed
Fix Version/s: 10.9.0.0
Thanks, Kathey, the DRDAConnThread
[
https://issues.apache.org/jira/browse/DERBY-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-4350.
---
Resolution: Duplicate
Resolving as duplicate of DERBY-5396, which fixed the issue
Thanks a lot for your answer.
But after few tries to use XPLAIN I did not succeed to learn any thing, I
always get an error message when I run :
CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
CALL SYSCS_UTIL.SYSCS_SET_STATISTICS_TIMING(1);
CALL SYSCS_UTIL.SYSCS_SET_XPLAIN_SCHEMA('MYAPP');
I
Do it this way:
CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
SELECT * FROM ;
VALUES SYSCS_UTIL.SYSCS_GET_RUNTIMESTATISTICS();
CALL SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(0);
Replace the SELECT * FROM ... with your query. The VALUES SYS... will
return one row, one column that contains
[
https://issues.apache.org/jira/browse/DERBY-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094608#comment-13094608
]
Bryan Pendleton commented on DERBY-5301:
The most recent patch looks great to me.
[Auto-generated mail]
*Daily* 1161617/2011-08-25 18:00:33 MEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
NA NA NANA suitesAll
NA NA NANA jdbcapiAutoLoad
NA
Thanks a lot.
Now I've got the following result :
Statement Name:
SQL_CURLH000C7
Statement Text:
SELECT * FROM CALLCDRACD WHERE clientId='' ORDER BY CALLSTART
OFFSET 10
ROWS FETCH NEXT 50 ROWS ONLY
Parse Time: 0
Bind Time: 0
Optimize Time: 0
Generate Time: 0
Compile Time:
[
https://issues.apache.org/jira/browse/DERBY-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4647:
--
Fix Version/s: 10.8.1.6
BaseTestCase.execJavaCmd() does not work with weme 6.2
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094668#comment-13094668
]
Rick Hillegas commented on DERBY-5363:
--
I think that the default embedded behavior
[
https://issues.apache.org/jira/browse/DERBY-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094675#comment-13094675
]
Kathey Marsden commented on DERBY-5347:
---
Are there thoughts on whether we should
Given the Sort it looks like index is not being used to avoid sorts.
I am not sure why that is the case. Does adding an index on just
CALLSTART help or not?
The OFFSET feature is relatively new to derby and I am not sure if the
optimizer has been fully updated to understand it. Maybe someone
Hi,
I've backported most of the issues for which I thought a backport was
reasonable and marked others with the reject_backport label.
I've been looking at this list based on a query Kathey set up in JIRA
(also referenced off the DerbyTenEightTwoRelease wiki page):
Hi,
We're about 12 days away from the date I picked to produce the
10.8.2.0 release candidate.
I finished backported fixes for a number of bugs (I don't intend to
backport a number of sql-to-junit conversions).
I am watching the following issues (some critical), hoping they'll get
fixed in time
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094750#comment-13094750
]
Kathey Marsden commented on DERBY-5363:
---
I think it would be good to get feedback
On 8/31/2011 10:32 AM, Myrna van Lunteren wrote:
But I've been also somewhat track of the actual commits, and for the
second time I noticed a bug which as far as I can see should've shown
up on the list, but hasn't: DERBY-5396.
Can anyone figure out why it doesn't match the query? I've stared
[
https://issues.apache.org/jira/browse/DERBY-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094760#comment-13094760
]
Kathey Marsden commented on DERBY-5010:
---
It seems the code may not be reachable so
[
https://issues.apache.org/jira/browse/DERBY-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden reopened DERBY-5378:
---
reopen to add backport reject label. Only relevant to trunk
Update Derby web site copyright
[
https://issues.apache.org/jira/browse/DERBY-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden closed DERBY-5378.
-
Resolution: Fixed
Update Derby web site copyright notice (2011)
[
https://issues.apache.org/jira/browse/DERBY-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden reopened DERBY-4533:
---
reopen to add backport reject label. Only relevant to trunk
Delete old releases from
[
https://issues.apache.org/jira/browse/DERBY-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden closed DERBY-4533.
-
Resolution: Fixed
Delete old releases from http://www.apache.org/dist
[
https://issues.apache.org/jira/browse/DERBY-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5395:
-
Attachment: SafeCacheViewer.java
Attaching SafeCacheViewer.java. This is a table function which
[
https://issues.apache.org/jira/browse/DERBY-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden reopened DERBY-5277:
---
reopen to add backport reject label as this only affects trunk
Intermittent OutOfMemoryErrors
[
https://issues.apache.org/jira/browse/DERBY-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094777#comment-13094777
]
Rick Hillegas commented on DERBY-5395:
--
Regression tests passed cleanly for me on
[
https://issues.apache.org/jira/browse/DERBY-5277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden closed DERBY-5277.
-
Resolution: Fixed
Intermittent OutOfMemoryErrors in BasicSetup.testTriggersWithLOBcolumns()
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094781#comment-13094781
]
Kathey Marsden commented on DERBY-5363:
---
I personally don't think we have a security
[
https://issues.apache.org/jira/browse/DERBY-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094826#comment-13094826
]
Force Rs commented on DERBY-5347:
-
I am not a Derby expert, but I do have significant
[
https://issues.apache.org/jira/browse/DERBY-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5395:
-
Attachment: releaseNote.html
Attaching the first rev of a release note for this issue.
By
[
https://issues.apache.org/jira/browse/DERBY-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094880#comment-13094880
]
Kathey Marsden commented on DERBY-5347:
---
Thank you for the input. I'll have it
[
https://issues.apache.org/jira/browse/DERBY-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-5301.
Resolution: Fixed
Fix Version/s: 10.9.0.0
Issue fix info: (was: [Patch
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5363:
-
Attachment: derby-5363-basic-2.stat
derby-5363-basic-2.diff
Uploading
[
https://issues.apache.org/jira/browse/DERBY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095094#comment-13095094
]
Jayaram Subramanian commented on DERBY-5359:
I also agree that we need to
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095095#comment-13095095
]
Dag H. Wanvik commented on DERBY-5363:
--
I am not sure that the property is backward,
On 8/31/2011 7:19 PM, Mike Matrigali wrote:
The OFFSET feature is relatively new to derby and I am not sure if the
optimizer has been fully updated to understand it. Maybe someone who
knows more about the OFFSET feature can comment if the optimizer has
been updated to know that this query is
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik reassigned DERBY-5363:
Assignee: Dag H. Wanvik
Tighten default permissions of DB files with = JDK6
[
https://issues.apache.org/jira/browse/DERBY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-5363:
-
Issue fix info: [Patch Available, Release Note Needed] (was: [Release
Note Needed])
Tighten
39 matches
Mail list logo
