[jira] Commented: (DERBY-4373) different results with network server vs. embedded on select from a temporary table with resultset cursor hold over commit

[ https://issues.apache.org/jira/browse/DERBY-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761442#action_12761442 ] Dag H. Wanvik commented on DERBY-4373: -- Looking at the repro, the "new result set" tha

[jira] Commented: (DERBY-4392) "Table/View / Constraint already exists in Schema 'APP'" in lang.CheckConstraintTest on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761434#action_12761434 ] Dag H. Wanvik commented on DERBY-4392: -- I think fixture execution order is the issue h

[jira] Commented: (DERBY-4393) lang.SequenceTest fails w/ "Sequence 'ALPHA_SEQ' already exists." on phoneME/cvm

[ https://issues.apache.org/jira/browse/DERBY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761431#action_12761431 ] Dag H. Wanvik commented on DERBY-4393: -- It seems the success of this test is dependent

[jira] Commented: (DERBY-3002) Add support for GROUP BY ROLLUP

[ https://issues.apache.org/jira/browse/DERBY-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761426#action_12761426 ] Dag H. Wanvik commented on DERBY-3002: -- Sure, +1. > Add support for GROUP BY ROLLUP

[jira] Created: (DERBY-4395) Column nullability handling appears to be incorrect in ROLLUP-style GROUP BY clauses, affects use in subqueries

Column nullability handling appears to be incorrect in ROLLUP-style GROUP BY clauses, affects use in subqueries --- Key: DERBY-4395 URL: https://issues.apa

[jira] Created: (DERBY-4396) Derby ROLLUP support in GROUP BY clause is a subset of the SQL Standard specified behavior

Derby ROLLUP support in GROUP BY clause is a subset of the SQL Standard specified behavior -- Key: DERBY-4396 URL: https://issues.apache.org/jira/browse/DERBY-4396

[jira] Created: (DERBY-4394) Add documentation for ROLLUP functionality in GROUP BY clause

Add documentation for ROLLUP functionality in GROUP BY clause - Key: DERBY-4394 URL: https://issues.apache.org/jira/browse/DERBY-4394 Project: Derby Issue Type: Sub-task

[jira] Commented: (DERBY-4372) Wrong result for simple join when index is created

[ https://issues.apache.org/jira/browse/DERBY-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761342#action_12761342 ] Mamta A. Satoor commented on DERBY-4372: Knut, does the fix need to be backported t

[jira] Commented: (DERBY-3634) Cannot use row_number() in ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761326#action_12761326 ] Dag H. Wanvik commented on DERBY-3634: -- The row_number() is part of SQL's OLAP machine

[jira] Commented: (DERBY-3634) Cannot use row_number() in ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761308#action_12761308 ] Micky Li commented on DERBY-3634: - Thank you, Dag. The OFFSET/FETCH function is suitable f

[jira] Updated: (DERBY-3809) Add a SHOW FUNCTONS command to ij

[ https://issues.apache.org/jira/browse/DERBY-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Leroux updated DERBY-3809: -- Attachment: show-functions-3.diff This time, I tried to narrow the result columns as much as po

Regression Test Report - Daily 820325 - Sun DBTG

[Auto-generated mail] *Daily* 820325/2009-09-30 18:02:16 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 01165211652 0 1045.45% suitesAll 01313 0 .% jdbcapiAutoLoad 012

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (18 issues) Subscriber: derby-dev Key Summary DERBY-4374 Document the CROSS JOIN operation in the reference manual https://issues.apache.org/jira/browse/DERBY-4374 DERBY-3634 Cannot use row_number() in

[jira] Updated: (DERBY-4374) Document the CROSS JOIN operation in the reference manual

[ https://issues.apache.org/jira/browse/DERBY-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-4374: - Attachment: DERBY-4374-2.zip DERBY-4374-2.diff Thanks, Knut! I'm attaching a revised patc

[jira] Commented: (DERBY-4373) different results with network server vs. embedded on select from a temporary table with resultset cursor hold over commit

[ https://issues.apache.org/jira/browse/DERBY-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761199#action_12761199 ] Knut Anders Hatlen commented on DERBY-4373: --- If the prefetching was causing this,

[jira] Commented: (DERBY-4374) Document the CROSS JOIN operation in the reference manual

[ https://issues.apache.org/jira/browse/DERBY-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761183#action_12761183 ] Knut Anders Hatlen commented on DERBY-4374: --- Thanks Kim! The docs look great. I'

[jira] Created: (DERBY-4393) lang.SequenceTest fails w/ "Sequence 'ALPHA_SEQ' already exists." on phoneME/cvm

lang.SequenceTest fails w/ "Sequence 'ALPHA_SEQ' already exists." on phoneME/cvm Key: DERBY-4393 URL: https://issues.apache.org/jira/browse/DERBY-4393 Project: Derby

[jira] Created: (DERBY-4392) "Table/View / Constraint already exists in Schema 'APP'" in lang.CheckConstraintTest on phoneME/cvm

"Table/View / Constraint already exists in Schema 'APP'" in lang.CheckConstraintTest on phoneME/cvm --- Key: DERBY-4392 URL: https://issues.apache.org/jira/browse/DERB

[jira] Commented: (DERBY-3002) Add support for GROUP BY ROLLUP

[ https://issues.apache.org/jira/browse/DERBY-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761165#action_12761165 ] Knut Anders Hatlen commented on DERBY-3002: --- +1 to the suggested approach. Gettin