[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: (was: [Patch Available]) Committed 'derby-3326-4a-cpdsc_shutEngine.diff' to

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572383#action_12572383 ] Jørgen Løland commented on DERBY-3463: -- Hi Ole, I tried to reproduce the first

Re: Regression Test Report - Daily 630637 - Sun DBTG

And although all systems came online again, some services were not available right away, causing no tests to be started. I hope and expect this to be solved for the next testcycle. Henri Henri van de Scheur wrote: Due to a power outage, all tests were aborted last night. Sorry for any

[jira] Updated: (DERBY-3469) Clob.length() doesn't detect a closed underlying connection in a consistent way

[ https://issues.apache.org/jira/browse/DERBY-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3469: --- Attachment: ClosedClobTest.java Attached a very simple repro ('ClosedClobTest.java'). To use

[jira] Created: (DERBY-3469) Clob.length() doesn't detect a closed underlying connection in a consistent way

Clob.length() doesn't detect a closed underlying connection in a consistent way --- Key: DERBY-3469 URL: https://issues.apache.org/jira/browse/DERBY-3469 Project: Derby

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572393#action_12572393 ] Ole Solberg commented on DERBY-3463: There is 40G free on the disk. 1) I also ran with

[jira] Updated: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3360: -- This issue seems to use either 'existing application impact' or 'release note needed'

[jira] Updated: (DERBY-646) In-memory backend storage support

[ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-646: - This issue seems to use either 'existing application impact' or 'release note needed' incorrectly,

[jira] Created: (DERBY-3468) Example in documentation of ij.exceptionTrace is wrong

Example in documentation of ij.exceptionTrace is wrong -- Key: DERBY-3468 URL: https://issues.apache.org/jira/browse/DERBY-3468 Project: Derby Issue Type: Bug Components:

[jira] Updated: (DERBY-3095) CALL SYSCS_UTIL.SYSCS_SET_USER_ACCESS(?, null) FAILS

[ https://issues.apache.org/jira/browse/DERBY-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3095: -- This issue seems to use either 'existing application impact' or 'release note needed'

[jira] Updated: (DERBY-3078) Better error messages needed when foreign key constraint creation fails because of delete-connection violations

[ https://issues.apache.org/jira/browse/DERBY-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3078: -- This issue seems to use either 'existing application impact' or 'release note needed'

[jira] Updated: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-2667: --- Attachment: derby-2667-WriteExceptionsToFileAsTheyHappen.diff

[jira] Commented: (DERBY-3445) Make it easier to use the EMMA tool to measure the code coverage of the Derby testing

[ https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572416#action_12572416 ] Vemund Østgaard commented on DERBY-3445: About DERBY-3153: - The additions of

[jira] Updated: (DERBY-3031) Improve Derby core plugin packaging structure (solving MANY problems)

[ https://issues.apache.org/jira/browse/DERBY-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3031: -- This issue seems to use either 'existing application impact' or 'release note needed'

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572414#action_12572414 ] Ole Solberg commented on DERBY-3463: I am now not able to reproduce 3). (And the logs

[jira] Updated: (DERBY-3456) Allow removing not null from collumns particpating in unique constraint.

[ https://issues.apache.org/jira/browse/DERBY-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3456: -- Attachment: upgradetests.diff This patch has upgrade tests for unique constraint. under soft

10.4 Feature Freeze

... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? Here is the current status (based on what I know): Feature Status -- SQL rolesDelayed (disabled) System

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572436#action_12572436 ] Ole Solberg commented on DERBY-3463: By adding a 10s sleep between failover and the

[jira] Updated: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3463: --- Attachment: min_index.tar Slave db is still in replication slave mode after failover if there was

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572431#action_12572431 ] Ole Solberg commented on DERBY-3463: Reproduced, see attachement min_index.tar. But

[jira] Updated: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-2998: -- Attachment: d2998-16.stat d2998-16.diff Thanks again for having a look Army!

[jira] Commented: (DERBY-3358) After an incorrect(unsuccesfull) startMaster comand, further correct startMaster attempts also fail.

[ https://issues.apache.org/jira/browse/DERBY-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572441#action_12572441 ] Øystein Grøvlen commented on DERBY-3358: Thanks, for your patch Narayanan. I tried

[jira] Commented: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572440#action_12572440 ] James Alan Shepherd commented on DERBY-3360: I am unable to use Derby in my

[jira] Resolved: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland resolved DERBY-3463. -- Resolution: Invalid It is according to spec to get the exception until failover is complete,

[jira] Closed: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg closed DERBY-3463. -- Slave db is still in replication slave mode after failover if there was replication load before

[jira] Issue Comment Edited: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572450#action_12572450 ] dyret edited comment on DERBY-3360 at 2/26/08 4:25 AM: To

[jira] Commented: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572450#action_12572450 ] Dyre Tjeldvoll commented on DERBY-3360: --- To quote from the link I mentioned:

[jira] Commented: (DERBY-3463) Slave db is still in replication slave mode after failover if there was replication load before failover.

[ https://issues.apache.org/jira/browse/DERBY-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572451#action_12572451 ] Øystein Grøvlen commented on DERBY-3463: I still miss an explanation for the

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572453#action_12572453 ] Dag H. Wanvik commented on DERBY-3465: -- I built this rev (630954) and ran it with Java

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572458#action_12572458 ] Dag H. Wanvik commented on DERBY-2667: -- Re

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572460#action_12572460 ] Kristian Waagan commented on DERBY-3465: I also tried to reproduce this, without

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572461#action_12572461 ] Kristian Waagan commented on DERBY-2667: Well, maybe I misunderstood, but if you

[jira] Commented: (DERBY-3437) Give all replication threads meaningfull names

[ https://issues.apache.org/jira/browse/DERBY-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572462#action_12572462 ] Øystein Grøvlen commented on DERBY-3437: Serge, thanks for the patch. It looks

[jira] Updated: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Alan Shepherd updated DERBY-3360: --- Derby Info: (was: [Existing Application Impact]) Invalid method java.lang.Integer

[jira] Commented: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572465#action_12572465 ] James Alan Shepherd commented on DERBY-3360: My apologies. My use was because

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572468#action_12572468 ] Dag H. Wanvik commented on DERBY-2667: -- Thanks, Kristian, I was not thinking of the

[jira] Closed: (DERBY-3421) Remove unused code for caching of connect bytes

[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3421. -- Remove unused code for caching of connect bytes ---

[jira] Closed: (DERBY-3357) Reduce runtime of jdbcapi.DataSourceTest

[ https://issues.apache.org/jira/browse/DERBY-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3357. -- Refactorings seems to be working fine, and I don't expect more work to be done. Closing issue,

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Derby Info: [Patch Available] 'testNetworkServerSecurityMechanism' fails with

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Attachment: derby-3465-1a-remove_try_catch.diff 'derby-3465-1a-remove_try_catch.diff'

[jira] Resolved: (DERBY-3438) Allow SQL query text to be null in StatementKey

[ https://issues.apache.org/jira/browse/DERBY-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan resolved DERBY-3438. Resolution: Fixed Committed 'derby-3438-1a-allow_sql_null.diff' to trunk with revision

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: ... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? Here is the current status (based on what I know): JMX On track JMX is on track per se, as it has not been defined what exactly will be

Optional permissions in policy files

Based on Dans suggestions to fix an issue with my patch for DERBY-3445, I read up a bit more on policy files and discovered a feature that can be used to make parts of the policy file optional. Since I didn't know about this feature myself, I thought I'd share it with the community, as I think

[jira] Updated: (DERBY-3192) Cache session data in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3192: -- Attachment: derby-3192-mark2.v7.diff OK, here is v7 which sends PBSD in SYNCCTLreply and uses

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: SQL OLAP (row-number)On track I hope to be able to wrap up the ROW_NUMBER() work over the next couple of days - but no guarantee as of now. Thomas -- Thomas Nielsen

[jira] Updated: (DERBY-3192) Cache session data in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3192: -- Attachment: derby-3192-mark2.v8.diff v8 moves parsePBSD() from Reply to NetConnection where it

[jira] Commented: (DERBY-2667) Create more robust junit TestRunner for running derby tests

[ https://issues.apache.org/jira/browse/DERBY-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572496#action_12572496 ] Kristian Waagan commented on DERBY-2667: Dag, it is a valid concern and I have not

[jira] Commented: (DERBY-3375) Localize new error messages added in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572499#action_12572499 ] Dyre Tjeldvoll commented on DERBY-3375: --- I plan to commit the v2 patch unless there

[jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572498#action_12572498 ] Thomas Nielsen commented on DERBY-2998: --- The resultset number problem is a little

[jira] Updated: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3205: - Attachment: failover-slave-2a.diff failover-slave-2a.stat Patch failover-slave

[jira] Created: (DERBY-3470) Replication: Master never gives up when slave dies.

Replication: Master never gives up when slave dies. --- Key: DERBY-3470 URL: https://issues.apache.org/jira/browse/DERBY-3470 Project: Derby Issue Type: Bug Components: Replication

[jira] Commented: (DERBY-3435) Add an MBean for monitoring and managing the Network Server

[ https://issues.apache.org/jira/browse/DERBY-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572504#action_12572504 ] John H. Embretsen commented on DERBY-3435: -- Thanks for helping out adding some

[jira] Issue Comment Edited: (DERBY-3375) Localize new error messages added in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572499#action_12572499 ] dyret edited comment on DERBY-3375 at 2/26/08 6:39 AM: I

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-6a-npe_fix_synch_CLC.diff 'derby-3326-6a-npe_fix_synch_CLC.diff'

[jira] Updated: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3205: - Derby Info: [Patch Available] Replication: Add connection url command options for starting,

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Hi Dyre, thanks for all the great work on the 10.4 release! I think we should remove the OLAP item from the list, as we haven't made much progress on it and there won't be much done for OLAP in the 10.4 release. It's

[jira] Commented: (DERBY-3360) Invalid method java.lang.Integer void init(short) because java.lang.NoSuchMethodException: java.lang.Integer.init(short)

[ https://issues.apache.org/jira/browse/DERBY-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572513#action_12572513 ] Kathey Marsden commented on DERBY-3360: --- James, can you attach a reproducible test

Re: 10.4 Feature Freeze

Bryan Pendleton wrote: [EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Hi Dyre, thanks for all the great work on the 10.4 release! I think we should remove the OLAP item from the list, as we haven't made much progress on it and there won't be much done for OLAP in

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-6b-npe_fix_synch_CLC.diff 'derby-3326-6b-npe_fix_synch_CLC.diff'

Re: 10.4 Feature Freeze

Jørgen Løland [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: Replication On track The 10.4 replication functionality is done, but I would be a lot more confident in this new functionality if we had the time to add a lot of tests. I would prefer that we move code-freeze to

Re: 10.4 Feature Freeze

Bryan Pendleton [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Hi Dyre, thanks for all the great work on the 10.4 release! I think we should remove the OLAP item from the list, as we haven't made much progress on it and there won't be

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572525#action_12572525 ] Dag H. Wanvik commented on DERBY-3465: -- I tried the patch and it ran cleanly on

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Feature Status -- System privilegesOn track Have you any more information on the state of this? Martin said he was working on a new patch

[jira] Updated: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-2998: -- Attachment: d2998-17.stat d2998-17.diff The culprit turned out to be

Re: 10.4 Feature Freeze

John Embretsen [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: ... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? Here is the current status (based on what I know): JMX On track JMX is on track per se, as it

[jira] Issue Comment Edited: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572531#action_12572531 ] thomanie edited comment on DERBY-2998 at 2/26/08 8:08 AM:

Re: 10.4 Feature Freeze

Daniel John Debrunner [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Feature Status -- System privilegesOn track Have you any more information on the state

[jira] Updated: (DERBY-3445) Make it easier to use the EMMA tool to measure the code coverage of the Derby testing

[ https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vemund Østgaard updated DERBY-3445: --- Attachment: 3445-testspecific-diffv2 3445-general-diffv2 Attaching new

[jira] Updated: (DERBY-3385) Tests for JMX Management and Monitoring

[ https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John H. Embretsen updated DERBY-3385: - Attachment: d3385_versionMBeanTest_01.diff Attaching patch

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] writes: SQL rolesDelayed (disabled) To clarify, not disabled on trunk, but will be on the 10.4 branch, tracked by DERBY-3460. Dag

[jira] Updated: (DERBY-3457) Closing a logical connection must close all associated logical statements

[ https://issues.apache.org/jira/browse/DERBY-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3457: --- Attachment: derby-3457-1b-stmt_closing.diff 'derby-3457-1b-stmt_closing.diff' is a refreshed

[jira] Commented: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572552#action_12572552 ] Kristian Waagan commented on DERBY-3465: Thank you for the review Dag. The test

[jira] Updated: (DERBY-3465) 'testNetworkServerSecurityMechanism' fails with 'junit.framework.AssertionFailedError: did not expect an sqlexception'.

[ https://issues.apache.org/jira/browse/DERBY-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3465: --- Description:

[jira] Updated: (DERBY-990) store/access.sql fails - incorrect index?

[ https://issues.apache.org/jira/browse/DERBY-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-990: - Fix Version/s: 10.1.3.2 store/access.sql fails - incorrect index?

[jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572556#action_12572556 ] A B commented on DERBY-2998: I have not had a chance to look at patch 17 yet, but I just had

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

Issue Subscription Filter: Derby: JIRA issues with patch available (28 issues) Subscriber: derby-dev Key Summary DERBY-3457 Closing a logical connection must close all associated logical statements https://issues.apache.org/jira/browse/DERBY-3457 DERBY-3445 Make it easier

Regression Test Report - Daily 630934 - Sun DBTG

[Auto-generated mail] *Daily* 630934/2008-02-25 18:01:06 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA

[jira] Updated: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3441: --- Derby Info: [Patch Available] Assignee: Kristian Waagan Determine and implement a

[jira] Updated: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3441: --- Attachment: derby-3441-1a-statement_reset.diff 'derby-3441-1a-statement_reset.diff' is the

Re: 10.4 Feature Freeze

Daniel John Debrunner wrote: [EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Feature Status -- System privilegesOn track Have you any more information on the state of this? Martin said

Branching and release.properties

Looking ahead to the upcoming branching for 10.4, I have some questions to the instructions at http://wiki.apache.org/db-derby/DerbySnapshotOrRelease The text instructs you to edit tools/ant/release.properties. But this file does not exist, but tools/ant/properties/release.properties does. I'm I

[jira] Commented: (DERBY-3464) NPE is seemingly simple query

[ https://issues.apache.org/jira/browse/DERBY-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572564#action_12572564 ] Shelly McGowan commented on DERBY-3464: --- Building the latest trunk, Apache Derby

Re: Branching and release.properties

[EMAIL PROTECTED] wrote: Looking ahead to the upcoming branching for 10.4, I have some questions to the instructions at http://wiki.apache.org/db-derby/DerbySnapshotOrRelease The text instructs you to edit tools/ant/release.properties. But this file does not exist, but

[jira] Commented: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable

[ https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572567#action_12572567 ] Mamta A. Satoor commented on DERBY-3304: Merged 631108 from trunk into 10.3.2.2

[jira] Issue Comment Edited: (DERBY-3304) Explicit commit inside a java procedure makes a dynamic result sets passed out unavailable

[ https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572374#action_12572374 ] mamtas edited comment on DERBY-3304 at 2/26/08 9:28 AM: -

Re: 10.4 Feature Freeze

Daniel John Debrunner wrote: [EMAIL PROTECTED] wrote: Here is the current status (based on what I know): Feature Status -- System privilegesOn track Have you any more information on the state of this? Martin said

[jira] Updated: (DERBY-3440) Run suites.All with statement pooling enabled and classify the problems occurring

[ https://issues.apache.org/jira/browse/DERBY-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3440: --- Attachment: WithCPDS-WithStatementPooling-errors-01.txt

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Derby Info: [Patch Available] Introduce a caching logical connection and logical prepared

[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver

[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-7a-prepare_column_indexes_names_fix.diff

Re: 10.4 Feature Freeze

[EMAIL PROTECTED] wrote: ... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? [snip - other work going on] Client stm cache On track I'm still working hard to get this done. In my last run of suites.All with connections obtained

[jira] Commented: (DERBY-2998) Add support for ROW_NUMBER() window function

[ https://issues.apache.org/jira/browse/DERBY-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572580#action_12572580 ] A B commented on DERBY-2998: Is this something that has been fixed with patch 17? Or is it

[jira] Commented: (DERBY-3441) Determine and implement a proper procedure for resetting a prepared statement for reuse in a statement pool

[ https://issues.apache.org/jira/browse/DERBY-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572588#action_12572588 ] Daniel John Debrunner commented on DERBY-3441: -- I think a list of what is

[jira] Commented: (DERBY-3385) Tests for JMX Management and Monitoring

[ https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572594#action_12572594 ] Daniel John Debrunner commented on DERBY-3385: -- I'll work on committing this.

Re: Branching and release.properties

Rick Hillegas wrote: [EMAIL PROTECTED] wrote: Looking ahead to the upcoming branching for 10.4, I have some questions to the instructions at http://wiki.apache.org/db-derby/DerbySnapshotOrRelease The text instructs you to edit tools/ant/release.properties. But this file does not exist, but

[jira] Assigned: (DERBY-3429) Remove system property derby.system.jmx

[ https://issues.apache.org/jira/browse/DERBY-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner reassigned DERBY-3429: Assignee: Daniel John Debrunner Remove system property derby.system.jmx

[jira] Closed: (DERBY-3429) Remove system property derby.system.jmx

[ https://issues.apache.org/jira/browse/DERBY-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner closed DERBY-3429. Resolution: Fixed Fix Version/s: 10.4.0.0 Property removed with Revision:

Re: 10.4 Feature Freeze

Kristian Waagan wrote: [EMAIL PROTECTED] wrote: ... is fast approaching (2008-02-29) Is this still a reasonable date, or should we consider delaying it? [snip - other work going on] Client stm cache On track I'm still working hard to get this done. In my last run of suites.All

[jira] Commented: (DERBY-3385) Tests for JMX Management and Monitoring

[ https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572618#action_12572618 ] Daniel John Debrunner commented on DERBY-3385: -- Patch committed as-is -

[jira] Commented: (DERBY-3445) Make it easier to use the EMMA tool to measure the code coverage of the Derby testing

[ https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572614#action_12572614 ] Daniel John Debrunner commented on DERBY-3445: -- + !-- ant 1.7 finds junit.jar

[jira] Commented: (DERBY-3385) Tests for JMX Management and Monitoring

[ https://issues.apache.org/jira/browse/DERBY-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572620#action_12572620 ] Daniel John Debrunner commented on DERBY-3385: -- Moved the utility code out of

  1   2   >