[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: derby-3162.3-v4c.stat.txt derby-3162.3-v4c.diff.txt Patch 3162.3-v4c

[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=12576070#action_12576070 ] Thomas Nielsen commented on DERBY-2998: --- Looks like the doc-3 patch still hasn't been

[jira] Updated: (DERBY-3388) Improve message handling for replication messages to derby.log

[ https://issues.apache.org/jira/browse/DERBY-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3388: -- Derby Info: (was: [Patch Available]) Committed revision 634586. Improve message

Re: NetworkServerTestSetup issues with starting server as a separate process

Daniel John Debrunner wrote: - The server is booted without setting derby.system.home. For the vm running the junit tests derby.system.home=${user.dir}/system. Since d.s.h is not set the server is running with a system home of user.dir. I think this explains the wombat database appearing in

Re: ant javadoc on trunk?

Army wrote: Narayanan wrote: I just let it stay and went to make my cup of coffee and on returning I found this (about half an hour I guess) [javadoc] java.lang.OutOfMemoryError: Java heap space [snip] It just keeps going, I am continuously getting java.lang.OutOfMemoryError: Java heap

Regression Test Report - tinderbox_trunk16 634541 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 634541/2008-03-07 06:22:14 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 1274273 095.31% derbyall 01039810398 0

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: (was: derby-3162.3-v4b.diff.txt) Create a framework for replication tests

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: (was: derby-3162.3-v4.stat.txt) Create a framework for replication tests

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: (was: derby-3162.3-v4.diff.txt) Create a framework for replication tests

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: (was: derby-3162.3-v4b.stat.txt) Create a framework for replication tests

Re: ant javadoc on trunk?

John Embretsen wrote: A quick look with JConsole indicates that the testing-javadoc JVM needs about 86 MB of heap space (on many systems the default is 64 MB). Note that this is the JVM running the javadoc tool, not Ant itself (Ant's javadoc task always forks the VM). So setting e.g.

[jira] Created: (DERBY-3507) startNetworkServer and stopNetworkServer don't pass arguments

startNetworkServer and stopNetworkServer don't pass arguments - Key: DERBY-3507 URL: https://issues.apache.org/jira/browse/DERBY-3507 Project: Derby Issue Type: Improvement

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anurag Shekhar updated DERBY-3502: -- Attachment: derby-3502v3.diff Description of derby-3502v3.diff fixed the new issue Army had

[jira] Created: (DERBY-3508) Log receiver thread fails with NPE at failover when master has died

Log receiver thread fails with NPE at failover when master has died --- Key: DERBY-3508 URL: https://issues.apache.org/jira/browse/DERBY-3508 Project: Derby Issue Type: Bug

[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=12576102#action_12576102 ] Jørgen Løland commented on DERBY-3358: -- I now understand why you are catching

[jira] Resolved: (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 ] Dyre Tjeldvoll resolved DERBY-2998. --- Resolution: Fixed Patch file: d2998-followup-doc3.diff Committed revision 634587. Add

[jira] Updated: (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:all-tabpanel ] V.Narayanan updated DERBY-3358: --- Attachment: Derby3358_v6.stat Derby3358_v6.diff On retrospection I think you are

[jira] Commented: (DERBY-3466) Investigate ability to run multiple Derby systems in same JVM with different sets of MBeans.

[ https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576119#action_12576119 ] John H. Embretsen commented on DERBY-3466: -- I agree we should not put too much

[jira] Updated: (DERBY-3434) Send master database to the slave location using the replication network

[ https://issues.apache.org/jira/browse/DERBY-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3434: - Affects Version/s: 10.5.0.0 Setting fix version to 10.5 since this feature will not make it in

[jira] Issue Comment Edited: (DERBY-3434) Send master database to the slave location using the replication network

[ https://issues.apache.org/jira/browse/DERBY-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576131#action_12576131 ] jorgenlo edited comment on DERBY-3434 at 3/7/08 2:52 AM: --

[jira] Updated: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level

[ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3427: -- Fix Version/s: 10.3.2.2 I'm adding 10.3.2.2 to the list of fix versions as I think this is a

[jira] Created: (DERBY-3509) The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.

The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException. - Key: DERBY-3509 URL:

[jira] Commented: (DERBY-3374) Hang in master server if startMaster command is given twice

[ https://issues.apache.org/jira/browse/DERBY-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576130#action_12576130 ] Jørgen Løland commented on DERBY-3374: -- Ole, I think this issue was fixed by patch 4

[jira] Updated: (DERBY-3496) CallableStatement with output parameter leaves cursor open after execution

[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3496: -- Fix Version/s: 10.4.0.0 10.3.2.2 Adding 10.3.2.2 and 10.4.0.0 as fix

[jira] Resolved: (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 resolved DERBY-3192. --- Resolution: Fixed I'm resolving this as I have not seen any regressions in the testing so

Re: svn commit: r634658 - /db/derby/code/trunk/java/engine/org/apache/derby/impl/services/replication/net/SocketConnection.java

[EMAIL PROTECTED] writes: Author: oysteing Date: Fri Mar 7 05:06:08 2008 New Revision: 634658 URL: http://svn.apache.org/viewvc?rev=634658view=rev Log: DERBY-3358: OOME at slave during replication Isn't this DERBY-3497? public void writeMessage(Object message) throws IOException {

[jira] Updated: (DERBY-3497) OOME at slave during replication

[ https://issues.apache.org/jira/browse/DERBY-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-3497: --- Derby Info: (was: [Patch Available]) Thanks, for fixing this Jørgen. Patch committed as

Re: svn commit: r634658 - /db/derby/code/trunk/java/engine/org/apache/derby/impl/services/replication/net/SocketConnection.java

Knut Anders Hatlen wrote: [EMAIL PROTECTED] writes: Author: oysteing Date: Fri Mar 7 05:06:08 2008 New Revision: 634658 URL: http://svn.apache.org/viewvc?rev=634658view=rev Log: DERBY-3358: OOME at slave during replication Isn't this DERBY-3497? Oops. I will fix that. public

[jira] Created: (DERBY-3510) NetworkServerTestSetup should use the same JVM version for spawned servers as the test itself

NetworkServerTestSetup should use the same JVM version for spawned servers as the test itself -- Key: DERBY-3510 URL: https://issues.apache.org/jira/browse/DERBY-3510

[jira] Updated: (DERBY-3432) Move replication code from org.apache.derby.impl.services.replication to o.a.d.i.store.replication

[ https://issues.apache.org/jira/browse/DERBY-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3432: - Attachment: derby-3432-1a.diff derby-3432-1a.stat The attached patch moves the

[jira] Commented: (DERBY-3510) NetworkServerTestSetup should use the same JVM version for spawned servers as the test itself

[ https://issues.apache.org/jira/browse/DERBY-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576209#action_12576209 ] John H. Embretsen commented on DERBY-3510: -- A potential improvement could be to

[jira] Commented: (DERBY-3466) Investigate ability to run multiple Derby systems in same JVM with different sets of MBeans.

[ https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576221#action_12576221 ] Daniel John Debrunner commented on DERBY-3466: -- Currently the system

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3162: --- Attachment: derby-3162.3-v4d.stat.txt derby-3162.3-v4d.diff.txt Patch 3162.3-v4d

[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_jdbcMBeanTest_01.diff Thanks for committing patch 02 for the

[jira] Updated: (DERBY-3493) stress.multi times out waiting on testers with blocked testers waiting on the same statement

[ https://issues.apache.org/jira/browse/DERBY-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3493: -- Attachment: d3493-1a.diff Attaching a patch which I believe solves the hang. The

[jira] Updated: (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:all-tabpanel ] Øystein Grøvlen updated DERBY-3358: --- Derby Info: (was: [Patch Available]) Thanks, Narayanan for the follow-up. Patch committed

[jira] Resolved: (DERBY-3432) Move replication code from org.apache.derby.impl.services.replication to o.a.d.i.store.replication

[ https://issues.apache.org/jira/browse/DERBY-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen resolved DERBY-3432. Resolution: Fixed Fix Version/s: 10.4.0.0 Thanks for the instruction and patch

[jira] Commented: (DERBY-3506) Add JMX testing with a security manager and JMX authentication.

[ https://issues.apache.org/jira/browse/DERBY-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576243#action_12576243 ] Daniel John Debrunner commented on DERBY-3506: -- Having added some code to pass

[jira] Assigned: (DERBY-3503) Change stress.multi to dump thread stacks before killing off testers with jdk 1.5 and higher

[ https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-3503: - Assignee: Kathey Marsden Change stress.multi to dump thread stacks before killing off

[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=12576250#action_12576250 ] Daniel John Debrunner commented on DERBY-3385: -- I'll commit the jdbc patch but

[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=12576251#action_12576251 ] Vemund Østgaard commented on DERBY-3445: You are correct, emma tries to read and

[jira] Commented: (DERBY-2085) Misleading error message for non-matching ORDER BY clause in queries with GROUP BY.

[ https://issues.apache.org/jira/browse/DERBY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576252#action_12576252 ] Dyre Tjeldvoll commented on DERBY-2085: --- I believe the error message in question was

[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=12576254#action_12576254 ] John H. Embretsen commented on DERBY-3385: -- OK, thanks! I kind of knew that, but

[jira] Created: (DERBY-3511) Cannot resolve functions which return VARCHAR FOR BIT DATA or LONG VARCHAR FOR BIT DATA

Cannot resolve functions which return VARCHAR FOR BIT DATA or LONG VARCHAR FOR BIT DATA --- Key: DERBY-3511 URL: https://issues.apache.org/jira/browse/DERBY-3511

[jira] Updated: (DERBY-3511) Cannot resolve functions which return VARCHAR FOR BIT DATA or LONG VARCHAR FOR BIT DATA

[ https://issues.apache.org/jira/browse/DERBY-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3511: - Attachment: byteArrayFunctions.sql BigStringMaker.java To demonstrate the

Reminder: Feature freeze is today!

Just a friendly reminder that feature freeze is today. Since we're a global community it seems fair to set the freeze point to midnight GMT+12, so there are still a few hours left :) -- dt

[jira] Updated: (DERBY-3503) Change stress.multi to dump thread stacks before killing off testers with jdk 1.5 and higher

[ https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3503: -- Attachment: derby-3503_diff.txt Attached is an initial patch for this issue, but it is not

Re: ant javadoc on trunk?

John Embretsen wrote: I see that some of the javadoc targets in build.xml include: additionalparam=-J-mx320M The javadoc build works for me when I add this to the testing-javadoc target as well. A quick look with JConsole indicates that the testing-javadoc JVM needs about 86 MB of heap

[jira] Updated: (DERBY-3512) Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR

[ https://issues.apache.org/jira/browse/DERBY-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3512: - Attachment: bigStrings.sql BigStringMaker.java To demonstrate the problem, do

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

Issue Subscription Filter: Derby: JIRA issues with patch available (13 issues) Subscriber: derby-dev Key Summary DERBY-3162 Create a framework for replication tests https://issues.apache.org/jira/browse/DERBY-3162 DERBY-3447 Shutdown on a database without stopping

[jira] Created: (DERBY-3512) Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR

Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR Key: DERBY-3512 URL:

[jira] Commented: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576271#action_12576271 ] A B commented on DERBY-3502: Thank you for the patch, Anurag--and esp. for updating the

Regression Test Report - Daily 634346 - Sun DBTG

[Auto-generated mail] *Daily* 634346/2008-03-06 18:07:59 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 2274272 091.24% derbyall 01032210322 0 1437.02% suitesAll linN+1

[jira] Created: (DERBY-3513) NullPointerException in newBrokeredStatement in app server environment

NullPointerException in newBrokeredStatement in app server environment -- Key: DERBY-3513 URL: https://issues.apache.org/jira/browse/DERBY-3513 Project: Derby Issue Type:

[jira] Updated: (DERBY-3513) NullPointerException in newBrokeredStatement in app server environment

[ https://issues.apache.org/jira/browse/DERBY-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3513: -- Description: User reports in an app server environment an intermittent NullPointerException

[jira] Updated: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-3162: --- Derby Info: (was: [Patch Available]) Thanks for the new tests, Ole. I have committed the

[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 ] Mike Matrigali updated DERBY-3456: -- Description: Enable alter table to change a column that participates in a unique constraint to

[jira] Commented: (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:comment-tabpanelfocusedCommentId=12576292#action_12576292 ] Anurag Shekhar commented on DERBY-3456: --- Thanks Mike for committing it. You have

Re: Reminder: Feature freeze is today!

[EMAIL PROTECTED] wrote: Just a friendly reminder that feature freeze is today. Since we're a global community it seems fair to set the freeze point to midnight GMT+12, so there are still a few hours left :) Hmmm, that makes feature freeze *yesterday*! :-) Dan.

[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=12576300#action_12576300 ] Daniel John Debrunner commented on DERBY-3445: -- Thinking a little more I'm not

[jira] Issue Comment Edited: (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=12576300#action_12576300 ] djd edited comment on DERBY-3445 at 3/7/08 9:52 AM: --

Re: [Db-derby Wiki] Update of DerbyTenFourRelease by DyreTjeldvoll

The following page has been changed by DyreTjeldvoll: || SQL Roles || Most of feature T331 and parts of T332 || [https://issues.apache.org/jira/browse/DERBY-2207 DERBY-2207] || Postponed || - || System privileges || Restrict who can shutdown engines and create databases||

[jira] Commented: (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:comment-tabpanelfocusedCommentId=12576308#action_12576308 ] A B commented on DERBY-3456: Minor observation: the error message 42Z20 currently says:

[jira] Commented: (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:comment-tabpanelfocusedCommentId=12576311#action_12576311 ] Anurag Shekhar commented on DERBY-3456: --- This error message is thrown while setting

build failure related to Unique Constraints

I am seeing the following build failure after syncing with the trunk. It looks like a test class was not checked in: [javac] /Users/rh161140/derby/mainline/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java:129: cannot find symbol [javac] symbol : variable

Re: build failure related to Unique Constraints

File is now in. Please update the workspace. anurag Rick Hillegas wrote: I am seeing the following build failure after syncing with the trunk. It looks like a test class was not checked in: [javac]

[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=12576314#action_12576314 ] Daniel John Debrunner commented on DERBY-3385: -- As a style issue I think the

Re: ant javadoc on trunk?

Army wrote: I assume it's okay for this change to be checked into the codeline, so I plan to commit it shortly. Committed with svn # 634773: URL: http://svn.apache.org/viewvc?rev=634773view=rev Thanks again for the pointer, John. Army

[jira] Commented: (DERBY-3162) Create a framework for replication tests

[ https://issues.apache.org/jira/browse/DERBY-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576322#action_12576322 ] Ole Solberg commented on DERBY-3162: Thanks Øystein, for your comments and committing

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

I have not looked at code so not sure how hard to determine which error to throw, but seems like you should add a new error message for the new code to use, and soft upgrade can continue to use the old message. This is assuming there is no SQL standard for this exact error number. Anurag

[jira] Updated: (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:all-tabpanel ] John H. Embretsen updated DERBY-3435: - Derby Info: [Patch Available] Add an MBean for monitoring and managing the Network

[jira] Updated: (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:all-tabpanel ] John H. Embretsen updated DERBY-3435: - Attachment: d3435_NetworkServerMBeanTest_v01.diff Attaching patch

[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=12576341#action_12576341 ] John H. Embretsen commented on DERBY-3385: -- OK, I will move the sysinfo code to

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

I will create a separate issue for it. Even though the amount of code changes will be very small it will end breaking several tests (relying on either state or message). anurag Mike Matrigali wrote: I have not looked at code so not sure how hard to determine which error to throw, but seems like

[jira] Updated: (DERBY-3341) TABLE FUNCTION returning CHAR values does not return a correct value if the Java ResultSet class returns a value less than the length of the defined CHAR.

[ https://issues.apache.org/jira/browse/DERBY-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3341: - Attachment: derby-3341-01-da-coerceWithTests.diff Attaching a second rev of a fix:

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

before coding, making patch could you make sure to write up exactly what you are planning on doing in the new issue. Want to make sure there are no upgrade/backward compatibility issues being introduced. Assuming there is no change in error behavior in soft upgrade mode, what is the exact

Regression Test Report - tinderbox_trunk16 634733 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 634733/2008-03-07 17:33:27 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 1274273 095.01% derbyall 01040810408 0

[jira] Updated: (DERBY-3341) TABLE FUNCTION returning CHAR values does not return a correct value if the Java ResultSet class returns a value less than the length of the defined CHAR.

[ https://issues.apache.org/jira/browse/DERBY-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3341: - Attachment: rrefcreatefunctionstatement.html derby-3341-02-aa-refGuide.diff

Re: Reminder: Feature freeze is today!

Daniel John Debrunner wrote: [EMAIL PROTECTED] wrote: Just a friendly reminder that feature freeze is today. Since we're a global community it seems fair to set the freeze point to midnight GMT+12, so there are still a few hours left :) Hmmm, that makes feature freeze *yesterday*! You are

[jira] Created: (DERBY-3514) SecureServerTest failing with timeout waiting for the network server to start only when run in derbynet._Suite

SecureServerTest failing with timeout waiting for the network server to start only when run in derbynet._Suite -- Key: DERBY-3514 URL:

[jira] Updated: (DERBY-3443) With IBM 1.6 derbynet/sysinfo.java, derbynet/sysinfo_withproperties and derbynet/getCurrentProperties fail with missing line listing properties

[ https://issues.apache.org/jira/browse/DERBY-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3443: -- Fix Version/s: 10.4.0.0 With IBM 1.6 derbynet/sysinfo.java, derbynet/sysinfo_withproperties

[jira] Assigned: (DERBY-2813) enable security manager for store/ClassLoaderBootTest

[ https://issues.apache.org/jira/browse/DERBY-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-2813: - Assignee: (was: Kathey Marsden) unassigning. I am not currently working on this

[jira] Closed: (DERBY-3443) With IBM 1.6 derbynet/sysinfo.java, derbynet/sysinfo_withproperties and derbynet/getCurrentProperties fail with missing line listing properties

[ https://issues.apache.org/jira/browse/DERBY-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-3443. - Resolution: Fixed With IBM 1.6 derbynet/sysinfo.java, derbynet/sysinfo_withproperties and

Re: [Db-derby Wiki] Update of DerbyTenFourRelease by DyreTjeldvoll

Daniel John Debrunner wrote: The following page has been changed by DyreTjeldvoll: || SQL Roles || Most of feature T331 and parts of T332 || [https://issues.apache.org/jira/browse/DERBY-2207 DERBY-2207] || Postponed || - || System privileges || Restrict who can shutdown engines and

[jira] Commented: (DERBY-3514) SecureServerTest failing with timeout waiting for the network server to start only when run in derbynet._Suite

[ https://issues.apache.org/jira/browse/DERBY-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576389#action_12576389 ] Daniel John Debrunner commented on DERBY-3514: -- Issue was due to an earlier

[jira] Commented: (DERBY-3341) TABLE FUNCTION returning CHAR values does not return a correct value if the Java ResultSet class returns a value less than the length of the defined CHAR.

[ https://issues.apache.org/jira/browse/DERBY-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576393#action_12576393 ] Daniel John Debrunner commented on DERBY-3341: -- For the record, my first

[jira] Updated: (DERBY-3503) Change stress.multi to dump thread stacks before killing off testers with jdk 1.5 and higher

[ https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3503: -- Derby Info: [Patch Available] Tests passed except for known issues. I verified stack traces

[jira] Commented: (DERBY-3512) Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR

[ https://issues.apache.org/jira/browse/DERBY-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576396#action_12576396 ] Daniel John Debrunner commented on DERBY-3512: -- It should match the behaviour

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3502: --- Fix Version/s: 10.4.0.0 Unique Constraint's backing index when shared with existing indexes doesn't behave as

[jira] Updated: (DERBY-3502) Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

[ https://issues.apache.org/jira/browse/DERBY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3502: --- Attachment: d3502v3_modified_1.diff I tweaked the v3 patch slightly by: a) Adding more comments to

[jira] Created: (DERBY-3515) 23 timeouts encountered while running management junit suite as part of full nightly runs.

23 timeouts encountered while running management junit suite as part of full nightly runs. -- Key: DERBY-3515 URL: https://issues.apache.org/jira/browse/DERBY-3515

[jira] Updated: (DERBY-3515) 23 timeouts encountered while running management junit suite as part of full nightly runs.

[ https://issues.apache.org/jira/browse/DERBY-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3515: -- Attachment: summary.out full list of 23 timeout errors. 23 timeouts encountered while

[jira] Commented: (DERBY-3512) Using functions, you can create a LONG VARCHAR value which is longer than the maximum length of a Derby LONG VARCHAR

[ https://issues.apache.org/jira/browse/DERBY-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576430#action_12576430 ] Rick Hillegas commented on DERBY-3512: -- Right, DERBY-3341 implements silent

[jira] Updated: (DERBY-3494) Move the setup of NormalizeResultSetNode into the NormalizeResultSetNode

[ https://issues.apache.org/jira/browse/DERBY-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3494: --- Attachment: d3494_npe_writeup.html Since the ResultColumnList of the original ResultSetNode correctly describes

[jira] Updated: (DERBY-3494) Move the setup of NormalizeResultSetNode into the NormalizeResultSetNode

[ https://issues.apache.org/jira/browse/DERBY-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3494: --- Attachment: d3494_npe_writeup.html Fix some minor formatting glitches in first version. Move the setup of

[jira] Resolved: (DERBY-3514) SecureServerTest failing with timeout waiting for the network server to start only when run in derbynet._Suite

[ https://issues.apache.org/jira/browse/DERBY-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner resolved DERBY-3514. -- Resolution: Fixed Fix Version/s: 10.4.0.0 Assignee: Daniel John

[jira] Created: (DERBY-3516) Set derby.system.home when NetworkServerTestSetup spawns the server in a separate JVM.

Set derby.system.home when NetworkServerTestSetup spawns the server in a separate JVM. -- Key: DERBY-3516 URL: https://issues.apache.org/jira/browse/DERBY-3516

[jira] Commented: (DERBY-3310) ASSERT in MergeSort.checkColumnTypes() disallow legal type conversions

[ https://issues.apache.org/jira/browse/DERBY-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576453#action_12576453 ] A B commented on DERBY-3310: Dan I don't think the ResultSetNode R should be modified. It's a

Regression Test Report - tinderbox_trunk16 634803 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 634803/2008-03-07 21:22:42 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 1274273 095.11% derbyall 01041510415 0

Re: [jira] Commented: (DERBY-3514) SecureServerTest failing with timeout waiting for the network server to start only when run in derbynet._Suite

Daniel John Debrunner (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576389#action_12576389 ] Daniel John Debrunner commented on DERBY-3514:

  1   2   >