[jira] Commented: (DERBY-4582) Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only).

[ https://issues.apache.org/jira/browse/DERBY-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861689#action_12861689 ] Knut Anders Hatlen commented on DERBY-4582: --- All tests passed. Committed patch 5a

[jira] Commented: (DERBY-4371) Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression

[ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861668#action_12861668 ] C.S. Nirmal J. Fernando commented on DERBY-4371: Hi Bryan, Okey, I underst

[jira] Commented: (DERBY-4371) Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression

[ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861661#action_12861661 ] Bryan Pendleton commented on DERBY-4371: It sounds like your proposed patch would c

[jira] Commented: (DERBY-4610) Error attempting delete with cascade and triggers

[ https://issues.apache.org/jira/browse/DERBY-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861660#action_12861660 ] Bryan Pendleton commented on DERBY-4610: Hmmm. That's a fairly subtle interaction.

[jira] Commented: (DERBY-4371) Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression

[ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861655#action_12861655 ] C.S. Nirmal J. Fernando commented on DERBY-4371: Thanks Bryan for help me o

[jira] Commented: (DERBY-4371) Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression

[ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861654#action_12861654 ] Bryan Pendleton commented on DERBY-4371: There's a bit of a trick to reading the fo

[jira] Commented: (DERBY-4371) Non-selected columns for SELECT DISTINCT allowed in ORDER BY clause if ordered by expression

[ https://issues.apache.org/jira/browse/DERBY-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861651#action_12861651 ] C.S. Nirmal J. Fernando commented on DERBY-4371: Hi Bryan, I ran Junit tes

Re: USING behavior

SELECT * FROM (T1 JOIN T2 USING (A)) JOIN T3 USING (A) The columns returned by the first join operator, T1 JOIN T2 USING (A), are: A, T1.B, T1.C, T2.B, T2.C (note: the column in the USING clause is only returned once, even though it exists both in T1 and T2) That's a subtle aspect of USING that

GSoC 2010

Hello all, I just wanted to thank the community for the vote of confidence for the second time in a row. I will do my very best not to disappoint and to finish my GSoC project successfully. I look forward to working with all of you again and if I can ever be of help, count me in! Regards, Tia

Re: Eclipse ui plugin for 10.6.1.0

Thanks, Myrna. I have signed the eclipse ui plugin which you attached to DERBY-4593 and parked it alongside the other release artifacts. Thanks, -Rick Myrna van Lunteren wrote: Rick, I can do this sometime tomorrow (Tue 4/27). Unless someone beats me to it. :-) Myrna On Mon, Apr 26, 2010 at

Re: 10.6 branch and fix versions in JIRA

On 04/27/10 20:14, Rick Hillegas wrote: > Knut Anders Hatlen wrote: >> Hi, >> >> There is no 10.6.1.1 fix version in JIRA, it seems. Should we add one so >> that we can tag fixes that go into the branch after the RC with it? (We >> should probably bump the version on the branch too. It still says 1

Re: 10.6 branch and fix versions in JIRA

Knut Anders Hatlen wrote: Hi, There is no 10.6.1.1 fix version in JIRA, it seems. Should we add one so that we can tag fixes that go into the branch after the RC with it? (We should probably bump the version on the branch too. It still says 10.6.1.0.) There is a 10.6.2.0 fix version, though, bu

[jira] Commented: (DERBY-4593) Track tasks needed to release Derby 10.6.1

[ https://issues.apache.org/jira/browse/DERBY-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861480#action_12861480 ] Rick Hillegas commented on DERBY-4593: -- Bumped the release id at the head of the 10.6

[jira] Updated: (DERBY-4582) Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only).

[ https://issues.apache.org/jira/browse/DERBY-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-4582: -- Attachment: derby-4582-5a-bugfix.diff Some of the code added in the 4a patch wasn't exe

[jira] Updated: (DERBY-4593) Track tasks needed to release Derby 10.6.1

[ https://issues.apache.org/jira/browse/DERBY-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-4593: -- Attachment: derby_ui_doc_plugin_1.1.2.zip Attaching the ui_doc_plugin 1.1.2 for use wit

[jira] Created: (DERBY-4633) Cache default calendar in result sets and statements on client driver

Cache default calendar in result sets and statements on client driver - Key: DERBY-4633 URL: https://issues.apache.org/jira/browse/DERBY-4633 Project: Derby Issue Type: Impr

[jira] Updated: (DERBY-4582) Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only).

[ https://issues.apache.org/jira/browse/DERBY-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-4582: -- Fix Version/s: 10.7.0.0 Issue & fix info: (was: [Patch Available]) Committed 4

10.6 branch and fix versions in JIRA

Hi, There is no 10.6.1.1 fix version in JIRA, it seems. Should we add one so that we can tag fixes that go into the branch after the RC with it? (We should probably bump the version on the branch too. It still says 10.6.1.0.) There is a 10.6.2.0 fix version, though, but I think we agreed that we

Re: instability in StreamingColumnTest

Thanks for investigating this, Kristian. Some comments inline... Kristian Waagan wrote: On 26.04.10 22:00, Rick Hillegas wrote: I saw the following error in StreamingColumnTest when run as part of the full JUnit suite on the 10.6 branch. I did not see this error when I ran that test standalone

Regression Test Report - Daily 938099 - Sun DBTG

[Auto-generated mail] *Daily* 938099/2010-04-26 18:00:24 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 01248312483 0 1794.12% suitesAll 01313 0 .% jdbcapiAutoLoad 012

Re: [VOTE] 10.6.1.0 release

Kim Haase wrote: I looked at db-derby-10.6.1.0-bin.tar.gz and db-derby-10.6.1.0-bin.zip. The docs appear to be fine except that they don't include Knut's very last checkin for DERBY-4401 yesterday (cosmetic fix to the syntax of INNER JOIN in the Ref Man). This is obviously not worth a respin i

Re: [VOTE] 10.6.1.0 release

On 04/27/10 16:17, Kim Haase wrote: > I looked at db-derby-10.6.1.0-bin.tar.gz and db-derby-10.6.1.0-bin.zip. > The docs appear to be fine except that they don't include Knut's very > last checkin for DERBY-4401 yesterday (cosmetic fix to the syntax of > INNER JOIN in the Ref Man). This is obvio

[jira] Commented: (DERBY-4401) Document USING clause in joins

[ https://issues.apache.org/jira/browse/DERBY-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861415#action_12861415 ] Knut Anders Hatlen commented on DERBY-4401: --- The last cosmetic fix was committed

Re: gentle reminder: buddy testers needed

Hi Jayaram, Thanks for testing the functionality so thoroughly! Please see my comments inline. On 04/27/10 14:14, Jayaram Subramanian wrote: > Thank Knut, > > But i observed one more thing... When i did > ResultSet rs=s.executeQuery("select * from t1 join t2 using (a) join > t3 using (a)"); the

Re: [VOTE] 10.6.1.0 release

I looked at db-derby-10.6.1.0-bin.tar.gz and db-derby-10.6.1.0-bin.zip. The docs appear to be fine except that they don't include Knut's very last checkin for DERBY-4401 yesterday (cosmetic fix to the syntax of INNER JOIN in the Ref Man). This is obviously not worth a respin in itself, but if t

[jira] Assigned: (DERBY-4587) Add tools for improved analysis and understanding of query plans and execution statistics

[ https://issues.apache.org/jira/browse/DERBY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C.S. Nirmal J. Fernando reassigned DERBY-4587: -- Assignee: C.S. Nirmal J. Fernando (was: Bryan Pendleton) > Add tools f

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

Issue Subscription Filter: Derby: JIRA issues with patch available (9 issues) Subscriber: derby-dev Key Summary DERBY-4582 Timestamps inserted with GMT calendar are 1 hour later when subsequently read with GMT calendar (Server Mode Only). https://issues.apache.org/jir

Re: gentle reminder: buddy testers needed

Thank Knut, But i observed one more thing... When i did ResultSet rs=s.executeQuery("select * from t1 join t2 using (a) join t3 using (a)"); the query went through and was able to produce results. But when i did s.executeQuery("select * from t1 join t2 using (a) join t3 using (c)"); the query

Re: instability in StreamingColumnTest

On 26.04.10 22:00, Rick Hillegas wrote: I saw the following error in StreamingColumnTest when run as part of the full JUnit suite on the 10.6 branch. I did not see this error when I ran that test standalone on that branch or on the trunk. Has anyone else seen this instability? Hi Rick, I had

[jira] Commented: (DERBY-4610) Error attempting delete with cascade and triggers

[ https://issues.apache.org/jira/browse/DERBY-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861292#action_12861292 ] Knut Anders Hatlen commented on DERBY-4610: --- The bug was caused by this part of t