Windows directory path in BUILDING.txt

Hi, I was Building the Derby on windows machine for which referred BUILDING.txt from my ${derby.source}. there was an example in section 3.2(Creating ant.properties) showing how to set j14lib which was like j14lib=C:\j2sdk1.4.2_10\jre\lib (for windows machine)

[jira] Commented: (DERBY-3320) Database creation and boot should fail if collation=TERRITORY_BASED and the selected locale is not supported

[ https://issues.apache.org/jira/browse/DERBY-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584028#action_12584028 ] Mamta A. Satoor commented on DERBY-3320: Committed changes into trunk with revision

[jira] Assigned: (DERBY-1201) ResultSet.updateRow() in network client should not throw an exception if no fields in the row have been modified.

[ https://issues.apache.org/jira/browse/DERBY-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suran Jayathilaka reassigned DERBY-1201: Assignee: Suran Jayathilaka ResultSet.updateRow() in network client should not

Re: 10.4 Jira filters available

[EMAIL PROTECTED] writes: Hi, I have create two public Jira filter, 'Derby 10.4 Release Note' and 'Derby 10.4 Fixed Bugs' which I plan to use when generating the release notes. Links and a brief description can be found at

[jira] Commented: (DERBY-3571) LOB locators are not released if the LOB columns are not accessed by the client

[ https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584049#action_12584049 ] Kristian Waagan commented on DERBY-3571: Thanks for all the reviewing Knut and

[jira] Updated: (DERBY-3584) Replication tests shall not be run on Java ME

[ https://issues.apache.org/jira/browse/DERBY-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3584: --- Derby Info: [Patch Available] Replication tests shall not be run on Java ME

Re: 10.4 Jira filters available

[EMAIL PROTECTED] writes: Knut Anders Hatlen [EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: Hi, I have create two public Jira filter, 'Derby 10.4 Release Note' and 'Derby 10.4 Fixed Bugs' which I plan to use when generating the release notes. Links and a brief description can be

Re: some comments on the 10.4 beta distribution

[EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: Kim Haase [EMAIL PROTECTED] writes: Good catches, Rick. Should there be a a JIRA issue for this? Or perhaps more than one? I think only the first two are specific to the docs. Also, which NOTICE are we talking about? The one in the code

[jira] Updated: (DERBY-3382) Replication: Slave must inform master if DBs are out of sync.

[ https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-3382: --- Fix Version/s: (was: 10.4.1.0) (was: 10.5.0.0)

[jira] Commented: (DERBY-3571) LOB locators are not released if the LOB columns are not accessed by the client

[ https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584086#action_12584086 ] Knut Anders Hatlen commented on DERBY-3571: --- b) You're of course right, I had

Re: some comments on the 10.4 beta distribution

[EMAIL PROTECTED] writes: Kim Haase [EMAIL PROTECTED] writes: Good catches, Rick. Should there be a a JIRA issue for this? Or perhaps more than one? I think only the first two are specific to the docs. Also, which NOTICE are we talking about? The one in the code trunk seems to have been

[jira] Updated: (DERBY-3584) Replication tests shall not be run on Java ME

[ https://issues.apache.org/jira/browse/DERBY-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3584: --- Attachment: derby-3584.1_v1.stat.txt Replication tests shall not be run on Java ME

Re: some comments on the 10.4 beta distribution

Kim Haase [EMAIL PROTECTED] writes: Good catches, Rick. Should there be a a JIRA issue for this? Or perhaps more than one? I think only the first two are specific to the docs. Also, which NOTICE are we talking about? The one in the code trunk seems to have been updated, and the one in the

Re: 10.4 Release Notes

Rick Hillegas [EMAIL PROTECTED] writes: Hi Dyre, Where would I go to find the latest version of the 10.4 release notes? The version bundled with the 10.4 beta seems to be sketchy. What's checked into the 10.4 branch appears to be a preliminary version of the 10.3 release notes. In the past,

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

[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3509: --- Attachment: Derby3509_1.stat Derby3509_1.diff I have modified the handleException

[jira] Commented: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

[ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584108#action_12584108 ] Anurag Shekhar commented on DERBY-3354: --- LobMapping and locater is used by the stored

Re: 10.4 Jira filters available

Knut Anders Hatlen [EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: Hi, I have create two public Jira filter, 'Derby 10.4 Release Note' and 'Derby 10.4 Fixed Bugs' which I plan to use when generating the release notes. Links and a brief description can be found at

[jira] Resolved: (DERBY-2911) Implement a buffer manager using java.util.concurrent classes

[ https://issues.apache.org/jira/browse/DERBY-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen resolved DERBY-2911. --- Resolution: Fixed Fix Version/s: 10.4.0.0 Merged the latest changes (rev.

[jira] Updated: (DERBY-3584) Replication tests shall not be run on Java ME

[ https://issues.apache.org/jira/browse/DERBY-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3584: --- Attachment: (was: derby-3584.1_v1.diff.txt) Replication tests shall not be run on Java ME

[jira] Closed: (DERBY-3576) Merge EngineBlob and EngineClob into a single interface

[ https://issues.apache.org/jira/browse/DERBY-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan closed DERBY-3576. -- Thanks for informing me about the problem Mamta. I have fixed it with revision 643326 and 643328

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

[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3509: --- Derby Info: [Patch Available] The replication log shipper is not notified when a new replication

Regression Test Report - tinderbox_trunk16 643295 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 643295/2008-04-01 08:22:22 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0274274 087.20% derbyall F:1,E:097659764 0

[jira] Updated: (DERBY-3584) Replication tests shall not be run on Java ME

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

[jira] Updated: (DERBY-3382) Replication: Slave must inform master if DBs are out of sync.

[ https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-3382: --- Fix Version/s: (was: 10.4.0.0) 10.5.0.0 10.4.1.0

[jira] Updated: (DERBY-3526) AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk

[ https://issues.apache.org/jira/browse/DERBY-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen updated DERBY-3526: --- Fix Version/s: 10.4.1.0 Fix merged to 10.4 branch at revision 643377. Merge command: svn

Re: Showstoppers

[EMAIL PROTECTED] writes: Is there an existing bug in Derby which you consider to be a showstopper for 10.4? (Meaning that you will veto the release unless this bug gets fixed). If this bug is not being actively worked on, please flag it here ASAP, so that those looking for bugs to fix can

Re: some comments on the 10.4 beta distribution

[EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: [EMAIL PROTECTED] writes: Kim Haase [EMAIL PROTECTED] writes: Good catches, Rick. Should there be a a JIRA issue for this? Or perhaps more than one? I think only the first two are specific to the docs. Also, which NOTICE are we talking

[jira] Updated: (DERBY-3327) SQL roles: Implement authorization stack (and SQL session context to hold it)

[ https://issues.apache.org/jira/browse/DERBY-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3327: - Attachment: DERBY-3327-4-full-e.stat DERBY-3327-4-full-e.diff Uploaded

[jira] Updated: (DERBY-2925) Prevent export from overwriting existing files

[ https://issues.apache.org/jira/browse/DERBY-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-2925: - Attachment: releaseNote.html Re-attaching release note as releaseNote.html since this is the

[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=12584147#action_12584147 ] Øystein Grøvlen commented on DERBY-3162: Patch 8 merged to 10.4 branch at revision

Regression Test Report - tinderbox_trunk16 643349 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 643349/2008-04-01 12:13:11 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0274274 087.04% derbyall F:1,E:097659764 0

[jira] Updated: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3073: - Derby Info: (was: [Existing Application Impact]) Unchecking Existing Application Impact for

[jira] Updated: (DERBY-2351) ORDER BY with expression with distinct in the select list returns incorrect result

[ https://issues.apache.org/jira/browse/DERBY-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-2351: - Attachment: releaseNote.html Scrubbed the release note so that it will survive the syntax checks

Re: 10.4 Release Notes

[EMAIL PROTECTED] wrote: Rick Hillegas [EMAIL PROTECTED] writes: Hi Dyre, Where would I go to find the latest version of the 10.4 release notes? The version bundled with the 10.4 beta seems to be sketchy. What's checked into the 10.4 branch appears to be a preliminary version of the 10.3

DERBY-3023: Does this issue need a release note?

DERBY-3023 fixes a bug in queries which mix INNER and OUTER joins. As a result of this fix, the same query may return different results in 10.3 and 10.4. This seems like a good reason to include a release note with this issue. Could we get a release note for this one? Thanks, -Rick

[jira] Resolved: (DERBY-3447) Shutdown on a database without stopping replication hangs

[ https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Øystein Grøvlen resolved DERBY-3447. Resolution: Fixed Fix Version/s: 10.4.1.0 Fix ported to 10.4 branch at revision

Re: (GSOC)Question about issue time

Junjie Peng wrote: Kathey: I want to report converting lang/big.sql as a new issue. But I'm busy in following days. Maybe I will spend over a week to finish this issue. I wonder, in this situation, whether a limiting factor of time exists? Must such kind of issue be finished in

Re: Windows directory path in BUILDING.txt

Hi Udai, thanks for investigating this issue. I was Building the Derby on windows machine for which referred BUILDING.txt from my ${derby.source}. there was an example in section 3.2 (Creating ant.properties) showing how to set j14lib which was like

[jira] Updated: (DERBY-3073) SQL roles: add parser support

[ https://issues.apache.org/jira/browse/DERBY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3073: - Derby Info: [Existing Application Impact] (was: [Existing Application Impact, Release Note

[jira] Updated: (DERBY-3561) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:2 but wa

[ https://issues.apache.org/jira/browse/DERBY-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John H. Embretsen updated DERBY-3561: - Attachment: Derby3561ReproStandalone.java

Re: Showstoppers

Knut Anders Hatlen wrote: [EMAIL PROTECTED] writes: Is there an existing bug in Derby which you consider to be a showstopper for 10.4? (Meaning that you will veto the release unless this bug gets fixed). If this bug is not being actively worked on, please flag it here ASAP, so that those

Re: some comments on the 10.4 beta distribution

Oh no ... I see the failure too. I found the problem -- I have incorrect capital letters in a cross-reference in src/ref/rrefattribstartmaster.dita: ixref href=rrefattribslaveHost.dita#rrefattribslaveHostslaveHost=hostname/xref/i I'm really sorry -- I mostly test on Windows, where the docs

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

Issue Subscription Filter: Derby: JIRA issues with patch available (16 issues) Subscriber: derby-dev Key Summary DERBY-3162 Create a framework for replication tests https://issues.apache.org/jira/browse/DERBY-3162 DERBY-3327 SQL roles: Implement authorization stack (and SQL

Regression Test Report - Daily 643037 - Sun DBTG

[Auto-generated mail] *Daily* 643037/2008-03-31 18:01:06 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1274273 084.93% derbyall F:1,E:097649763 0 1290.68% suitesAll sles

[jira] Commented: (DERBY-3583) Derby should throw a better error message if a BLOB/CLOB column is accessed more than once

[ https://issues.apache.org/jira/browse/DERBY-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584193#action_12584193 ] Kathey Marsden commented on DERBY-3583: --- When I implemented this change I saw test

[jira] Updated: (DERBY-3169) Add documentation for replication

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

[jira] Commented: (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:comment-tabpanelfocusedCommentId=12584210#action_12584210 ] Mamta A. Satoor commented on DERBY-3494: Kathey, I took a look at the patch and it

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584219#action_12584219 ] Kim Haase commented on DERBY-3552: -- Thanks for the explanation, Narayanan. I guess the jar

Re: 10.4 Jira filters available

Knut Anders Hatlen wrote: Or perhaps two different queries would be better? For improvement and wish, I think it makes sense to list all, since people who want to improve something on trunk only often skip the affects version or set it to the current trunk version. For bugs, the above query

Re: 10.4 Jira filters available

Dyre Tjeldvoll wrote: Knut Anders Hatlen wrote: Or perhaps two different queries would be better? For improvement and wish, I think it makes sense to list all, since people who want to improve something on trunk only often skip the affects version or set it to the current trunk version. For

Re: 10.4 Release Notes

Rick Hillegas wrote: Hi Dyre, I have fixed most of these issues as follows: DERBY-3073: I unchecked the Existing Application Impact and Release Note Needed because this work has been disabled on the 10.4 branch,. DERBY-2925: I renamed the release note to be releaseNote.html, which is

[jira] Updated: (DERBY-3575) Optimize client side LOB release mechanism by reducing the number of round-trips

[ https://issues.apache.org/jira/browse/DERBY-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3575: --- Fix Version/s: (was: 10.4.1.0) (was: 10.5.0.0) After getting

[jira] Commented: (DERBY-3169) Add documentation for replication

[ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584268#action_12584268 ] Kim Haase commented on DERBY-3169: -- Committed DERBY-3169-6.diff to docs trunk at revision

Re: DERBY-3023: Does this issue need a release note?

Rick Hillegas wrote: DERBY-3023 fixes a bug in queries which mix INNER and OUTER joins. Could we get a release note for this one? I can try to write something up later tonight (PST), Army

[jira] Updated: (DERBY-3571) LOB locators are not released if the LOB columns are not accessed by the client

[ https://issues.apache.org/jira/browse/DERBY-3571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3571: --- Attachment: derby-3571-2a-simple_release.stat

[jira] Commented: (DERBY-3583) Derby should throw a better error message if a BLOB/CLOB column is accessed more than once

[ https://issues.apache.org/jira/browse/DERBY-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584289#action_12584289 ] Kristian Waagan commented on DERBY-3583: As I noted in DERBY-3571, I believe that

Re: Showstoppers

Rick Hillegas wrote: 4) It might be worthwhile for the community to focus on bug fixing for a couple months. That could include a concentrated effort to track down these corruptions. +1

[jira] Created: (DERBY-3585) Document user authentication support for network server shutdown

Document user authentication support for network server shutdown Key: DERBY-3585 URL: https://issues.apache.org/jira/browse/DERBY-3585 Project: Derby Issue Type: Sub-task

[jira] Updated: (DERBY-3585) Document user authentication support for network server shutdown

[ https://issues.apache.org/jira/browse/DERBY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun updated DERBY-3585: --- Attachment: releaseNote.html Attached is the releaseNote.html describing the usage changes and

Re: Showstoppers

Kathey Marsden wrote: [EMAIL PROTECTED] wrote: Is there an existing bug in Derby which you consider to be a showstopper for 10.4? I think we definitely should wait for the documentation updates and release note for DERBY-2109 changes that impact users. I don't think there is a separate Jira

[jira] Assigned: (DERBY-3537) Invalid use shutdown authentication checks in NetworkServerControlImpl.directShutdown()

[ https://issues.apache.org/jira/browse/DERBY-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun reassigned DERBY-3537: -- Assignee: Martin Zaun Invalid use shutdown authentication checks in

[jira] Resolved: (DERBY-3537) Invalid use shutdown authentication checks in NetworkServerControlImpl.directShutdown()

[ https://issues.apache.org/jira/browse/DERBY-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun resolved DERBY-3537. Resolution: Fixed Fix Version/s: 10.4.0.0 Changes committed, resolving this issue.

Re: [VOTE] John H Embretsen as a Derby committer

+1 On Wed, Mar 26, 2008 at 9:13 AM, Daniel John Debrunner [EMAIL PROTECTED] wrote: John is actively involved on both the derby-dev and derby-user lists and fully engages in open development. He has had a number of patches committed, most recently taking the stalled JMX work and getting it

[jira] Assigned: (DERBY-3543) NetworkServerControl with user password but no command does not give usage message

[ https://issues.apache.org/jira/browse/DERBY-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun reassigned DERBY-3543: -- Assignee: Martin Zaun NetworkServerControl with user password but no command does not give

[jira] Commented: (DERBY-3585) Document user authentication support for network server shutdown

[ https://issues.apache.org/jira/browse/DERBY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584354#action_12584354 ] Kathey Marsden commented on DERBY-3585: --- Thanks Martin for the release note. I have

[jira] Updated: (DERBY-3543) NetworkServerControl with options but no command does not give usage message

[ https://issues.apache.org/jira/browse/DERBY-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun updated DERBY-3543: --- Derby Info: [Patch Available] Summary: NetworkServerControl with options but no command does

[jira] Created: (DERBY-3586) Remove am.Connection.reset(LogWriter,ClientBaseDataSource,boolean) and called methods

Remove am.Connection.reset(LogWriter,ClientBaseDataSource,boolean) and called methods - Key: DERBY-3586 URL: https://issues.apache.org/jira/browse/DERBY-3586

[jira] Updated: (DERBY-3585) Document user authentication support for network server shutdown

[ https://issues.apache.org/jira/browse/DERBY-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun updated DERBY-3585: --- Attachment: releaseNote.html I found with some experimenting that it also worked to use the

[jira] Updated: (DERBY-3586) Remove am.Connection.reset(LogWriter,ClientBaseDataSource,boolean) and called methods

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

Re: [VOTE] Thomas Nielsen as a Derby committer

+1 Bryan Pendleton wrote: I propose that Thomas Nielsen shall be a Derby committer. Over the last 6 months, I've worked with Thomas on some Derby features (http://wiki.apache.org/db-derby/OLAPOperations) as well as on some fairly sophisticated bug fixes, including

Re: [VOTE] John H Embretsen as a Derby committer

+1 Daniel John Debrunner wrote: John is actively involved on both the derby-dev and derby-user lists and fully engages in open development. He has had a number of patches committed, most recently taking the stalled JMX work and getting it into a shape where it could be committed to allow

[jira] Commented: (DERBY-2109) System privileges

[ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584379#action_12584379 ] Martin Zaun commented on DERBY-2109: Created DERBY-3585 for Release Note and

Regression Test Report - tinderbox_trunk16 643645 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 643645/2008-04-02 01:32:15 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0274274 086.97% derbyall F:1,E:097659764 0

[jira] Updated: (DERBY-3023) Different result rows depending on the sequence of INNER JOIN and OUTER JOIN

[ https://issues.apache.org/jira/browse/DERBY-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3023: --- Attachment: releaseNote.html Attaching a release note for this issue. I had to use MS Word to create the file and

[jira] Updated: (DERBY-3288) wrong query result in presence of a unique index

[ https://issues.apache.org/jira/browse/DERBY-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3288: --- Attachment: releaseNote.html I don't know if fixes for wrong results *regressions* really need a release note or

[jira] Updated: (DERBY-3279) Derby 10.3.X ignores ORDER BY DESC when target column has an index and is used in an OR clause or an IN list.

[ https://issues.apache.org/jira/browse/DERBY-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3279: --- Attachment: releaseNote.html I don't know if fixes for wrong results *regressions* really need a release note or