[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587887#action_12587887 ] Knut Anders Hatlen commented on DERBY-3347: --- Thanks for reviewing the patch, Dag!

[jira] Updated: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2871: -- Derby Info: (was: [Patch Available]) Committed revision 647078. (derbyall and suites.All

[jira] Resolved: (DERBY-2871) XATransactionTest gets XaException: Error executing a XAResource.commit(), server returned XAER_PROTO.

[ https://issues.apache.org/jira/browse/DERBY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll resolved DERBY-2871. --- Resolution: Fixed XATransactionTest gets XaException: Error executing a

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587898#action_12587898 ] Knut Anders Hatlen commented on DERBY-3347: --- I committed the 2a patch to trunk

[jira] Updated: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3347: -- Attachment: d3347-1b.diff The 1b patch replaces the 1a patch. It only contains one

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587919#action_12587919 ] Thomas Nielsen commented on DERBY-3603: --- Seems my comment formatting was messed up -

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587894#action_12587894 ] Thomas Nielsen commented on DERBY-3603: --- Looking at the queryplans I see something

[jira] Commented: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587926#action_12587926 ] Thomas Nielsen commented on DERBY-3603: --- oneRowRightSide is set during code

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587928#action_12587928 ] Dag H. Wanvik commented on DERBY-3347: -- Agreed, I think. Although the two methods it

[jira] Updated: (DERBY-2953) Dump the information about rollbacks of the global transaction (introduced in DERBY-2220 and DERBY-2432) to derby.log

[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-2953: -- Derby Info: (was: [Patch Available]) Dump the information about rollbacks of the global

[jira] Commented: (DERBY-2953) Dump the information about rollbacks of the global transaction (introduced in DERBY-2220 and DERBY-2432) to derby.log

[ https://issues.apache.org/jira/browse/DERBY-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587938#action_12587938 ] Dyre Tjeldvoll commented on DERBY-2953: --- Is this issue a true subset of DERBY-2871?

[jira] Closed: (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 closed DERBY-3497. -- OOME at slave during replication Key:

[jira] Closed: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen closed DERBY-3489. -- I have verified that this issue is fixed. Error message XRE04 does not include the right port

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

[ https://issues.apache.org/jira/browse/DERBY-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen closed DERBY-3470. -- Issue seems to have been fixed as part of other replication JIRAs. Replication: Master never

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587948#action_12587948 ] Knut Anders Hatlen commented on DERBY-3347: --- Thanks again, Dag. Patch 1b has been

[jira] Closed: (DERBY-2674) Stop running jdbc40 tests in the old test framework

[ https://issues.apache.org/jira/browse/DERBY-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen closed DERBY-2674. -- All JDBC 4 tests are now part of the Junit All suite. Stop running jdbc40 tests in the old test

[jira] Updated: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3347: -- Derby Info: [Regression] (was: [Regression, Patch Available]) Fix Version/s:

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587955#action_12587955 ] Knut Anders Hatlen commented on DERBY-3347: --- I guess we should try to back-port

[jira] Commented: (DERBY-3611) ERROR XSDG2: Invalid checksum on Page occurs during mass inserts into two-column bigint PK table

[ https://issues.apache.org/jira/browse/DERBY-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587959#action_12587959 ] Knut Anders Hatlen commented on DERBY-3611: --- OK, thanks, I'll try to do that.

[jira] Created: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2 - Key: DERBY-3613 URL: https://issues.apache.org/jira/browse/DERBY-3613 Project: Derby Issue Type: Bug Affects

[VOTE CANCELLED] 10.4.1.1 release candidate

The fact that a fix appears to be available for https://issues.apache.org/jira/browse/DERBY-3347 (and maybe DERBY-3611) which is a serious data corruption, AND that the investigation has shown that this is a regression in 10.3 (caused by DERBY-801), has convinced me that the right thing to do is

[jira] Commented: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

[ https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587984#action_12587984 ] Bryan Pendleton commented on DERBY-3613: Can you provide an example SQL script,

[jira] Updated: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3347: -- Fix Version/s: 10.4.1.2 +1 to merging to 10.4 (I added 10.4.1.2 as a fix-version, and have

[jira] Created: (DERBY-3614) Granted SystemPermissions are ignored when granted later with same target and different action

Granted SystemPermissions are ignored when granted later with same target and different action -- Key: DERBY-3614 URL: https://issues.apache.org/jira/browse/DERBY-3614

[jira] Commented: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

[ https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588001#action_12588001 ] Artur Kuś commented on DERBY-3613: -- Simple : CREATE TABLE tabla_name(field varchar(10),

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

Issue Subscription Filter: Derby: JIRA issues with patch available (5 issues) Subscriber: derby-dev Key Summary DERBY-2892 Closing a resultset after retrieving a large 32665 bytes value with Network Server does not release locks

[jira] Commented: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

[ https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588003#action_12588003 ] Bryan Pendleton commented on DERBY-3613: I believe you get two rows because the

[jira] Commented: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

[ https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588004#action_12588004 ] Artur Kuś commented on DERBY-3613: -- Thanks. It is very funny. Oracle, MSDE and Postgres

[jira] Updated: (DERBY-3227) Remove final from all getConnection() methods in EmbeddedDataSource

[ https://issues.apache.org/jira/browse/DERBY-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3227: -- Attachment: derby-3227.diff I have attached a patch which implements Aaron's suggestion. We

Regression Test Report - Daily 646856 - Sun DBTG

[Auto-generated mail] *Daily* 646856/2008-04-10 18:00:59 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0269269 084.07% derbyall 098819881 0 1374.61% suitesAll sles 0

[jira] Commented: (DERBY-3613) SELECT DISTINCT field FROM TABLE_NAME GROUP BY field, field2

[ https://issues.apache.org/jira/browse/DERBY-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588007#action_12588007 ] Bryan Pendleton commented on DERBY-3613: Derby might be interpreting the standards

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

[EMAIL PROTECTED] wrote: I plan to do this as soon as the fix for DERBY-3347 has been merged to the 10.4 branch, and then call for a vote on the new RC. It would be great also to see the alternate fix for DERBY-2892 go in and then it will eliminate the necessity for the release note and

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

I plan to do this as soon as the fix for DERBY-3347 has been merged to the 10.4 branch, and then call for a vote on the new RC. I'm not sure I understand why the availability of additional fixes required the cancellation of the previous vote. It seems to me that there are always additional

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

Kathey Marsden [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: I plan to do this as soon as the fix for DERBY-3347 has been merged to the 10.4 branch, and then call for a vote on the new RC. It would be great also to see the alternate fix for DERBY-2892 go in and then it will

[jira] Updated: (DERBY-3223) SQL roles: make use of privileges granted to roles in actual privilege checking

[ https://issues.apache.org/jira/browse/DERBY-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3223: - Attachment: derby-3223-1a.stat derby-3223-1a.diff Uploading an experimental

[jira] Updated: (DERBY-3603) 'IN' clause ignores valid results, incorrect qualifier handling suspected

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3603: --- Attachment: d3603_v1.patch The fact that oneRowRightSide is true for the NestedLoop join does indeed appear to be

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

Bryan Pendleton [EMAIL PROTECTED] writes: I plan to do this as soon as the fix for DERBY-3347 has been merged to the 10.4 branch, and then call for a vote on the new RC. I'm not sure I understand why the availability of additional fixes required the cancellation of the previous vote. It

[jira] Updated: (DERBY-3612) Developer's Guide needs correction on garbage collection

[ https://issues.apache.org/jira/browse/DERBY-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-3612: - Attachment: tdevdvlp20349.html DERBY-3612.diff Attaching DERBY-3612.diff and

[jira] Updated: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3574: Attachment: (was: derby3574-lob-java.patch) With client, attempting to get the lob

[jira] Updated: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3574: Attachment: (was: derby3574-clob-java.patch) With client, attempting to get the lob

[jira] Updated: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3574: Attachment: (was: derby3574-connection-java.patch) With client, attempting to get the

[jira] Updated: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3574: Attachment: (was: derby3574-blob-java.patch) With client, attempting to get the lob

[jira] Updated: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3574: Attachment: derby3574-wtest.patch With client, attempting to get the lob length after

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588069#action_12588069 ] Tiago R. Espinha commented on DERBY-3574: - I have just talked with Kathey on IRC

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

On 4/11/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Bryan Pendleton [EMAIL PROTECTED] writes: I plan to do this as soon as the fix for DERBY-3347 has been merged to the 10.4 branch, and then call for a vote on the new RC. I'm not sure I understand why the availability of additional

[jira] Issue Comment Edited: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588069#action_12588069 ] espinha edited comment on DERBY-3574 at 4/11/08 12:27 PM: ---

[jira] Updated: (DERBY-3223) SQL roles: make use of privileges granted to roles in actual privilege checking

[ https://issues.apache.org/jira/browse/DERBY-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3223: - Attachment: roles.sql Thanks for the patch, Dag. I've attached a test case (roles.sql), which

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588094#action_12588094 ] Kathey Marsden commented on DERBY-3574: --- Changes look good. Could you run regression

[jira] Updated: (DERBY-3223) SQL roles: make use of privileges granted to roles in actual privilege checking

[ https://issues.apache.org/jira/browse/DERBY-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3223: - Attachment: roles2.sql Attaching another puzzling case, roles2.sql. This test does the

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

Myrna van Lunteren wrote: On 4/11/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: [snip] I too had understood a Release Candidate to become a Release once approved. Now that there is a plan for a new release candidate, I think maybe the javadoc should be fixed? There are the following

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588128#action_12588128 ] Knut Anders Hatlen commented on DERBY-3347: --- I have merged the fixes to the 10.4

jsr169 build

I am trying to figure out what is the difference between jsr169 and jdbc3 which requires that we use the small platform jars in order to build Derby's J2ME support. I have tried the following experiment on the four source files which comprise our jsr169 support (the classnames which end in

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

Myrna van Lunteren wrote: Now that there is a plan for a new release candidate, I think maybe the javadoc should be fixed? There are the following errors: [javadoc] C:\svn\10.4\java\engine\org\apache\derby\iapi\jdbc\DRDAServerStarter.java:107: warning - @param argument address is not a

Re: jsr169 build

Hi Rick, JSR 169, removes some interfaces and methods on interfaces (example Array and ResultSet.getArray(), Connection.getTypeMap()) Rick Hillegas wrote: I am trying to figure out what is the difference between jsr169 and jdbc3 which requires that we use the small platform jars in order to

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588145#action_12588145 ] Bogdan Calmac commented on DERBY-3347: -- I can rerun my endurance test next week using

[jira] Commented: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588163#action_12588163 ] Knut Anders Hatlen commented on DERBY-3347: --- Thanks Bogdan, that would be great!

[jira] Commented: (DERBY-3612) Developer's Guide needs correction on garbage collection

[ https://issues.apache.org/jira/browse/DERBY-3612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588181#action_12588181 ] Martin Zaun commented on DERBY-3612: Hi Kim, while your changes on the garbage

why would Derby not restart unless EmbeddedDriver was unloaded?

If anyone knows, please comment on https://issues.apache.org/jira/browse/DERBY-3612 Thx, Martin

Re: [VOTE CANCELLED] 10.4.1.1 release candidate

On 4/11/08, Martin Zaun [EMAIL PROTECTED] wrote: Myrna van Lunteren wrote: Now that there is a plan for a new release candidate, I think maybe the javadoc should be fixed? There are the following errors: [javadoc]

[jira] Updated: (DERBY-3347) ERROR XSDB3: Container information cannot change once written

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3347: -- Attachment: WorkerThread.java MiniStress.java In working on another issue I