[jira] Commented: (DERBY-2443) Implement ResultSet updateClob/updateBlob methods on the NetworkClient

[ https://issues.apache.org/jira/browse/DERBY-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480683 ] Kristian Waagan commented on DERBY-2443: In ResultSetJDBC30Test: @@ -118,7 +118,7 @@ if (usingEm

Re: Thread Aware Issue..!!

Bryan Pendleton wrote: what does it mean by MT and thread aware in the context of java source files..!! This is a pretty complicated subject. Here's a good place to start: http://www.awprofessional.com/bookstore/product.asp?isbn=0201310090&rl=1 I recently read through another book on conc

Re: svn commit: r517610 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/CollatorSQLChar.java

Mamta Satoor wrote: Thanks, Knut, for taking care of javadoc diff caused by my checkin. Thanks for fixing mine too :) -- Kristian Mamta On 3/13/07, [EMAIL PROTECTED] * <[EMAIL PROTECTED] > wrote: Author: kahatlen Date: Tue

[jira] Updated: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-47: In my writeup on the diffs, ignore the comments about there being a possible bug. I incorrectly thought

Re: [jira] Commented: (DERBY-2390) DOCS - Merge Working with Derby and Getting Started Guide

"Kim Haase (JIRA)" <[EMAIL PROTECTED]> writes: > Kim Haase commented on DERBY-2390: > -- > On rgsdocs17307.html -- just a few things: > > I'm glad you caught the problem with the term "library. I don't > think Derby is technically a product, which implies something

[jira] Commented: (DERBY-2412) Refactor NetworkServerControlImpl

[ https://issues.apache.org/jira/browse/DERBY-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480614 ] Daniel John Debrunner commented on DERBY-2412: -- bernt> Refactor ... bugs ... When I'm refactoring code

[jira] Commented: (DERBY-1343) It is possible to have duplicate entries in conglomerateId of sysconglomerates before DERBY-655 was fixed in 10.0 or 10.1 databases. It is desirable to patch these datab

[ https://issues.apache.org/jira/browse/DERBY-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480611 ] Daniel John Debrunner commented on DERBY-1343: -- I stumbled across this bug as part of the cleanup for DE

Re: [jira] Updated: (DERBY-47) Some possible improvements to IN optimization

It is confusing just looking at the diff, the diff only tells the story about what locks exist after the first fetch from the cursor. Below is the output for that portion of the diff in the new code. The way to read this test is it does an operation, then gets all the locks outstanding, then

[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480575 ] Jean T. Anderson commented on DERBY-2398: - Dan wrote: > Testing the values is best as the purpose (I assume)

[jira] Updated: (DERBY-2429) Convert jdbcapi/resultset.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2429: -- Attachment: DERBY_2429.diff Attached is the patch for this issue. Tests migrated to new test:

[jira] Closed: (DERBY-2401) change client setTransactionIsolation to only commit when the isolation level is changed to match embedded

[ https://issues.apache.org/jira/browse/DERBY-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner closed DERBY-2401. Resolution: Duplicate Duplicate of DEBRY-2064 > change client setTransactionIsolat

[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480571 ] Daniel John Debrunner commented on DERBY-2398: -- jta> 6) I assume that what matters about the key generat

[jira] Commented: (DERBY-2401) change client setTransactionIsolation to only commit when the isolation level is changed to match embedded

[ https://issues.apache.org/jira/browse/DERBY-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480570 ] Stan Bradbury commented on DERBY-2401: -- It's been a week since Knut identified this as a duplicate of DERBY-2064

Re: [jira] Updated: (DERBY-47) Some possible improvements to IN optimization

Mike Matrigali updated DERBY-47: I took a look at the diffs in readlocks and I believe all are "correct" with respect to your changes. Thank you very, *very* much for such a detailed review of the readlocks diff, Mike. Not only does this answer the question of

[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480564 ] Jean T. Anderson commented on DERBY-2398: - Incidently, in the old test, tests 11 and 12 output this message:

[jira] Updated: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-47: I took a look at the diffs in readlocks and I believe all are "correct" with respect to your changes. I

[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480559 ] Jean T. Anderson commented on DERBY-2398: - 2) I think I can answer my own question: yes (I remembered belated

Re: Question about prefetch and exceptions

Kathey Marsden wrote: With derby client, if I do a select and the exception occurs on the third row, I do not get the first two rows of data. With embedded I get the first two rows. I assume this is because client prefetches the data, but I wonder if client should report the first two rows

[jira] Closed: (DERBY-2441) The documentation for NULLIF could be improved

[ https://issues.apache.org/jira/browse/DERBY-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-2441. - > The documentation for NULLIF could be improved > -- > >

[jira] Resolved: (DERBY-2441) The documentation for NULLIF could be improved

[ https://issues.apache.org/jira/browse/DERBY-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden resolved DERBY-2441. --- Resolution: Invalid Kim pointed out that this had already been resolved. I was looking at ol

Question about prefetch and exceptions

With derby client, if I do a select and the exception occurs on the third row, I do not get the first two rows of data. With embedded I get the first two rows. I assume this is because client prefetches the data, but I wonder if client should report the first two rows of data as well. Doe

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480548 ] A B commented on DERBY-681: --- > Do you think it makes sense to mark this bug as resolved and another to track > this issue.

[jira] Commented: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480546 ] A B commented on DERBY-47: -- > 1) In one of the comments, you said: > >We intentionally use a parameter node instead of a

[jira] Commented: (DERBY-2441) The documentation for NULLIF could be improved

[ https://issues.apache.org/jira/browse/DERBY-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480543 ] Kim Haase commented on DERBY-2441: -- Is the documentation in this location (http://db.apache.org/derby/manuals/refer

Re: Comments in StoredFormatIds refer to classes that do not exist. Are these just leftover comments that don't apply anymore?

Thanks for your time, Mike. Thanks for confirming my thought that these are more than likely just stale comments. Mamta On 3/13/07, Mike Matrigali <[EMAIL PROTECTED]> wrote: It is likely that they can be deleted, that they refer to stuff the predates the derby codeline. I can't think of any

[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2398: Attachment: derby-2398-pre.diff derby-2398-pre.diff converts about half of jdbcapi/autoGene

Re: [VOTE] Dag Wanvik as a committer

+1 On 3/12/07, Rick Hillegas <[EMAIL PROTECTED]> wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. Last year, Dag lead a team of developers in implementing Scrollable Updatable ResultSets. Recently h

Re: svn commit: r517610 - /db/derby/code/trunk/java/engine/org/apache/derby/iapi/types/CollatorSQLChar.java

Thanks, Knut, for taking care of javadoc diff caused by my checkin. Mamta On 3/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: kahatlen Date: Tue Mar 13 02:35:39 2007 New Revision: 517610 URL: http://svn.apache.org/viewvc?view=rev&rev=517610 Log: Fixed javadoc warning. Modified:

Re: Thread Aware Issue..!!

what does it mean by MT and thread aware in the context of java source files..!! This is a pretty complicated subject. Here's a good place to start: http://www.awprofessional.com/bookstore/product.asp?isbn=0201310090&rl=1 thanks, bryan

[jira] Commented: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480534 ] Bryan Pendleton commented on DERBY-47: -- Hi Army, I had a look at the preprocess and master patches and they look g

Thread Aware Issue..!!

hi, I am student working on Derby for implementing a new locking protocol.I have a small doubt regarding the Threads..!! what does it mean by MT and thread aware in the context of java source files..!! Thank You..!! -- **

[jira] Commented: (DERBY-2247) provide set methods for blob in embeded driver

[ https://issues.apache.org/jira/browse/DERBY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480521 ] Suresh Thalamati commented on DERBY-2247: - While doing some testing I ran into the LOBStreamControl.java in

Re: Should COLLATION attribute related code go in BasicDatabase?

That's right. The code to read COLLATION attribute can simply live in DataValueFactory.boot rather than in BasicDatabase.boot method. I will work on what's outline in this email thread. thanks, Mamta On 3/13/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: Mamta Satoor wrote: > Hi, > > Ba

[jira] Commented: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480516 ] Suresh Thalamati commented on DERBY-2020: - Olav, Thanks for finding more details about rws/rwd. 1) I wou

Re: Comments in StoredFormatIds refer to classes that do not exist. Are these just leftover comments that don't apply anymore?

It is likely that they can be deleted, that they refer to stuff the predates the derby codeline. I can't think of any persistent datatype that we got rid of since 10.0. To be absolutely safe one should check the 10.0 codeline as I can imagine horrible issues with reusing an existing format id

[jira] Updated: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2020: -- I have been convinced by Olav's recent posting that it is ok to use rwd - I won't block this chan

Re: Should COLLATION attribute related code go in BasicDatabase?

Mamta Satoor wrote: Hi, Based on the discussion in DERBY-2336 (Enable collation based ordering for CHAR data type.), we want to move towards making DataValueFactory keep track of locale related stuff. In order to move in that direction, I think the knowledge that user has requested territory

[jira] Commented: (DERBY-2427) jdbcapi/BlobStoredProcedureTest and jdbcapi/ClobStoredProcedureTest fail with weme6.1

[ https://issues.apache.org/jira/browse/DERBY-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480505 ] Daniel John Debrunner commented on DERBY-2427: -- These procedures just for use by the network server and

Re: commit of insert/uptate/delete transactions

the derby engine and I need to know exactly the point in the commit procedure where data is actually written or updates on disk. I don't think it works that way. The *log* is written to disk at commit time, but the *data* need not be. The data is written to buffered pages in memory, and pages

commit of insert/uptate/delete transactions

Hi all, I'm new to this list and also to the derby source code, so sorry for my newbie questions. I'm intercepting some important points of transaction processing inside the derby engine and I need to know exactly the point in the commit procedure where data is actually written or updates

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480501 ] Manish Khettry commented on DERBY-681: -- OK. Do you think it makes sense to mark this bug as resolved and another

Junit conversion (was -Re: JIRA developer access request)

Ugo Matrangolo wrote: I would want to begin to add my little help to the project starting fixing bugs and writing test code until i reach sufficient code knowledge to move toward more complex tasks. Welcome to the development community Ugo! There is currently an effort underway to convert

Regression Test Report - Daily 517280 - Sun DBTG

[Auto-generated mail] *Daily* 517280/2007-03-12 18:00:27 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0419419 089.09% derbyall 069626962 0 398.89% suitesAll sles 0

Should COLLATION attribute related code go in BasicDatabase?

Hi, Based on the discussion in DERBY-2336 (Enable collation based ordering for CHAR data type.), we want to move towards making DataValueFactory keep track of locale related stuff. In order to move in that direction, I think the knowledge that user has requested territory based collation should a

Re: [VOTE] Dag Wanvik as a committer

Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. +1 Kathey

Re: [VOTE] Dag Wanvik as a committer

On 3/12/07, Rick Hillegas <[EMAIL PROTECTED]> wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. +1 Myrna

[jira] Created: (DERBY-2449) Unexpected NUMALLOCATEDPAGES, NUMFREEPAGES, ESTIMSPACESAVING for conglomerate.

Unexpected NUMALLOCATEDPAGES, NUMFREEPAGES, ESTIMSPACESAVING for conglomerate. --- Key: DERBY-2449 URL: https://issues.apache.org/jira/browse/DERBY-2449 Project: Derby

[jira] Updated: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-47: - Attachment: readlocks_withContext.diff Atttaching the readlocks diff with more context to hopefully help in reviewing...

Re: [VOTE] Dag Wanvik as a committer

Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. +1 Army

Re: [jira] Updated: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

Knut Anders Hatlen wrote: A B updated DERBY-681: -- I ran derbyall with the latest patch and there was one unexpected failure (Derby client only): *** Start: setTransactionIsolation jdk1.4.2 DerbyNetClient [snip] However, I re-ran the test without your changes and it sti

[jira] Commented: (DERBY-2390) DOCS - Merge Working with Derby and Getting Started Guide

[ https://issues.apache.org/jira/browse/DERBY-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480439 ] Kim Haase commented on DERBY-2390: -- Excellent start on this, Laura! cgsintro.html looks just fine. Good catch on t

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

Issue Subscription Filter: Derby: JIRA issues with patch available (22 issues) Subscriber: derby-dev Key Summary DERBY-2020 Change file option for syncing log file to disk from rws to rwd https://issues.apache.org/jira/browse/DERBY-2020 DERBY-2386 timestampdiff function fail

Re: JIRA developer access request

Ugo Matrangolo wrote: > Dear derby-dev, > > Hi. My name is Ugo Matrangolo and I'm asking you for a developer access to > the derby's JIRA. > I already have an account on the JIRA (username = matra). Hi, Ugo, you're now in the developers list. welcome, -jean

[jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses

[ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480437 ] A B commented on DERBY-681: --- Actually, it turns out that just switching to "visibleSize()" does *not* solve the problem. I

[jira] Updated: (DERBY-1704) Allow more concurrency in the lock manager

[ https://issues.apache.org/jira/browse/DERBY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-1704: -- Attachment: cleanup6.diff Attaching a new small cleanup patch (cleanup6) for LockSet.ja

[jira] Commented: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480432 ] Knut Anders Hatlen commented on DERBY-2020: --- I agree that alternative 2 sounds best. I'll try to explain t

[jira] Commented: (DERBY-2431) Documentation for DatabaseMetaData should reflect that getColumnPrivileges and getTablePrivileges are implemented

[ https://issues.apache.org/jira/browse/DERBY-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480430 ] Kim Haase commented on DERBY-2431: -- I'm not the authority on this, but I think I can answer these: getBestRowIdenti

[jira] Commented: (DERBY-2220) Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

[ https://issues.apache.org/jira/browse/DERBY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480421 ] Julius Stroffek commented on DERBY-2220: I am sorry, Knut, I misunderstood the comment about merging to 10.2,

[jira] Commented: (DERBY-2020) Change file option for syncing log file to disk from rws to rwd

[ https://issues.apache.org/jira/browse/DERBY-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480411 ] Olav Sandstaa commented on DERBY-2020: -- Thanks for the comments, Knut Anders. I will go through the comments and

[jira] Commented: (DERBY-2386) timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals

[ https://issues.apache.org/jira/browse/DERBY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480401 ] Daniel John Debrunner commented on DERBY-2386: -- The comment about bind time is related to what return ty

[jira] Commented: (DERBY-2264) Restrict shutdown, upgrade, and encryption powers to the database owner

[ https://issues.apache.org/jira/browse/DERBY-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480398 ] Rick Hillegas commented on DERBY-2264: -- Thanks for the patch, Dag. This looks like solid incremental improvement

[jira] Updated: (DERBY-1704) Allow more concurrency in the lock manager

[ https://issues.apache.org/jira/browse/DERBY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-1704: -- Attachment: cleanup5.stat cleanup5.diff cleanup5.diff contains these ch

Re: [VOTE] Dag Wanvik as a committer

+1 Julo Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. Last year, Dag lead a team of developers in implementing Scrollable Updatable ResultSets. Recently he investigated how to imp

[jira] Commented: (DERBY-1620) SQL CASE statement returns ERROR 42X89 when including NULL as a return value

[ https://issues.apache.org/jira/browse/DERBY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480389 ] John Peterson commented on DERBY-1620: -- I did run the entire test suite against it, and none of the problems th

[jira] Commented: (DERBY-2327) Reduce monitor contention in LockSet

[ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480388 ] Knut Anders Hatlen commented on DERBY-2327: --- Committed 3a with revision 517680. > Reduce monitor contentio

[jira] Updated: (DERBY-2327) Reduce monitor contention in LockSet

[ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2327: -- Attachment: derby-2327-3a.diff derby-2327-3a.diff makes the methods in Deadlock.java ta

Re: [VOTE] Dag Wanvik as a committer

+1 Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. Last year, Dag lead a team of developers in implementing Scrollable Updatable ResultSets. Recently he investigated how to implemen

JIRA developer access request

Dear derby-dev, Hi. My name is Ugo Matrangolo and I'm asking you for a developer access to the derby's JIRA. I already have an account on the JIRA (username = matra). I'm experimenting with Derby for a while both at work and home. I would want to begin to add my little help to the project start

Re: [VOTE] Dag Wanvik as a committer

+1 Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. -- With regards, Henri van de Scheur, Database Technology Group, Sun Microsystems, Trondheim, Norway

Re: [VOTE] Dag Wanvik as a committer

+1 Rick Hillegas wrote: > Please vote on whether we should make Dag Wanvik a Derby committer. The > vote will close at 5:00 pm San Francisco time on Monday March 19. -- Ole Solberg, Database Technology Group, Sun Microsystems, Trondheim, Norway

[jira] Created: (DERBY-2448) derbynet/checkSecMgr.java fails with 'Should have gotten security Exception'

derbynet/checkSecMgr.java fails with 'Should have gotten security Exception' - Key: DERBY-2448 URL: https://issues.apache.org/jira/browse/DERBY-2448 Project: Derby

Re: [VOTE] Dag Wanvik as a committer

Please vote on whether we should make Dag Wanvik a Derby committer. +1 -- Kristian

[jira] Created: (DERBY-2447) ejbql and floattypes in org.apache.derbyTesting.functionTests.tests.lang.LangScripts intermittently fails with 'expected:<[0.0 ] > but was:<[-0.0] '

ejbql and floattypes in org.apache.derbyTesting.functionTests.tests.lang.LangScripts intermittently fails with 'expected:<[0.0 ] > but was:<[-0.0] ' ---

[jira] Commented: (DERBY-1704) Allow more concurrency in the lock manager

[ https://issues.apache.org/jira/browse/DERBY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480311 ] Knut Anders Hatlen commented on DERBY-1704: --- Committed cleanup4.diff with 517588. > Allow more concurrency

[jira] Updated: (DERBY-2327) Reduce monitor contention in LockSet

[ https://issues.apache.org/jira/browse/DERBY-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-2327: -- Derby Info: (was: [Patch Available]) Committed 2a with revision 517586. > Reduce mon

[jira] Commented: (DERBY-2430) setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively

[ https://issues.apache.org/jira/browse/DERBY-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480307 ] V.Narayanan commented on DERBY-2430: Thank you for the commit knut. This patch blocks issue 2443 and this commit