[jira] Commented: (DERBY-3313) JDBC client driver statement cache

[ https://issues.apache.org/jira/browse/DERBY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559388#action_12559388 ] Kristian Waagan commented on DERBY-3313: Bryan wrote: Thanks Kristian! Are the

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

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559407#action_12559407 ] Øystein Grøvlen commented on DERBY-3205: If I first try to start the slave with

[jira] Commented: (DERBY-3318) Missing clean-up after failed startMaster

[ https://issues.apache.org/jira/browse/DERBY-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559409#action_12559409 ] Øystein Grøvlen commented on DERBY-3318: Note also that the error message of the

[jira] Commented: (DERBY-3221) java.sql.SQLException: The conglomerate (-5) requested does not exist. from Derby 10.3.1.4 embedded within Eclipse 3.3 and RAD 7.0

[ https://issues.apache.org/jira/browse/DERBY-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559410#action_12559410 ] Knut Anders Hatlen commented on DERBY-3221: --- Patch v2 looks good. Adding a getter

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

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559413#action_12559413 ] Øystein Grøvlen commented on DERBY-3205: I still get the assert if try to connect

Blockers and 10.4

Currently we have two JIRA issues classified as Blockers: https://issues.apache.org/jira/browse/DERBY-3260 and https://issues.apache.org/jira/browse/DERBY-3303 DERBY-3260 has a patch which has been reviewed favorably by Knut, but I feel that the following quote from his comment deserves some

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

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559421#action_12559421 ] Øystein Grøvlen commented on DERBY-3205: The code for the startSlave_1c.diff looks

[jira] Updated: (DERBY-3321) NullPointerException for 'NOT EXISTS' with nested subquery

[ https://issues.apache.org/jira/browse/DERBY-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3321: - Attachment: derby.log Attached derby.log. This issue also applies to 'exists', i.e. the same

[jira] Created: (DERBY-3321) NullPointerException for 'NOT EXISTS' with nested subquery

NullPointerException for 'NOT EXISTS' with nested subquery -- Key: DERBY-3321 URL: https://issues.apache.org/jira/browse/DERBY-3321 Project: Derby Issue Type: Bug Components:

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

[ https://issues.apache.org/jira/browse/DERBY-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559431#action_12559431 ] Dyre Tjeldvoll commented on DERBY-3192: --- I'm currently creating a writeup which

[jira] Updated: (DERBY-3254) Implement the replication failover functionality

[ https://issues.apache.org/jira/browse/DERBY-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3254: --- Attachment: failover_impl_v3.stat failover_impl_v3.diff The stopmaster patch had a

[jira] Commented: (DERBY-2185) Referene manual has conflicting information on when the territory attribute can be specified on the jdbc url.

[ https://issues.apache.org/jira/browse/DERBY-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559455#action_12559455 ] Dyre Tjeldvoll commented on DERBY-2185: --- Is DERBY-3179 a duplicate of this? Or at

[jira] Commented: (DERBY-1992) Upgrade to DITA Open Toolkit version 1.3

[ https://issues.apache.org/jira/browse/DERBY-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559457#action_12559457 ] Dyre Tjeldvoll commented on DERBY-1992: --- Not much activity on this issue lately. I

[jira] Commented: (DERBY-3254) Implement the replication failover functionality

[ https://issues.apache.org/jira/browse/DERBY-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559458#action_12559458 ] Øystein Grøvlen commented on DERBY-3254: Thanks for the patch, Narayanan. Her are

[jira] Commented: (DERBY-3129) Create Demo code, showing how to create and use table functions.

[ https://issues.apache.org/jira/browse/DERBY-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559460#action_12559460 ] Dyre Tjeldvoll commented on DERBY-3129: --- Hi Rick, can this issue be resolved/closed,

[jira] Resolved: (DERBY-3072) User documentation for Table Functions

[ https://issues.apache.org/jira/browse/DERBY-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll resolved DERBY-3072. --- Resolution: Fixed I think this is done User documentation for Table Functions

[jira] Closed: (DERBY-3072) User documentation for Table Functions

[ https://issues.apache.org/jira/browse/DERBY-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-3072. - I believe this is complete. User documentation for Table Functions

[jira] Commented: (DERBY-716) Re-enable VTIs

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559466#action_12559466 ] Dyre Tjeldvoll commented on DERBY-716: -- Hi Rick, can we resolve/close this now? As you

[jira] Commented: (DERBY-2983) The ResultSet returned by DatabaseMetaData.getFunctions() does not contain a required column named FUNCTION_TYPE.

[ https://issues.apache.org/jira/browse/DERBY-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559467#action_12559467 ] Dyre Tjeldvoll commented on DERBY-2983: --- Should this be resloved/closed? The

[jira] Resolved: (DERBY-3297) Document SIGN, SQRT, RAND, RANDOM, COSH, COT, SINH and TANH functions.

[ https://issues.apache.org/jira/browse/DERBY-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll resolved DERBY-3297. --- Resolution: Fixed Fixed Document SIGN, SQRT, RAND, RANDOM, COSH, COT, SINH and TANH

[jira] Resolved: (DERBY-3217) ErrorStreamTest failing on ibm j9 jvm

[ https://issues.apache.org/jira/browse/DERBY-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll resolved DERBY-3217. --- Resolution: Fixed Fix checked in ErrorStreamTest failing on ibm j9 jvm

[jira] Updated: (DERBY-3260) NullPointerException caused by race condition in GenericActivationHolder

[ https://issues.apache.org/jira/browse/DERBY-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3260: -- Attachment: d3260.diff I think this patch (d3260.diff) which narrows down the

[jira] Closed: (DERBY-3138) Optimizer error when vtis are invoked with correlated references to outer query blocks

[ https://issues.apache.org/jira/browse/DERBY-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-3138. - Committed resolved in October Optimizer error when vtis are invoked with correlated references to

Re: Customizing the Network Server's security policy (docs vs. reality)

Rick Hillegas wrote: I found that my custom policy worked (starting server, connecting, creating database, writing and reading data, shutting down...) even if I did not set derby.system.home (explicitly) and did not replace ${derby.system.home} in my policy file. Does this mean that we may

[jira] Closed: (DERBY-2701) many sealing violation errors in ibm142 and ibm15 jvm test runs of junit tests.

[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-2701. - many sealing violation errors in ibm142 and ibm15 jvm test runs of junit tests.

[jira] Closed: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-2608. - Compilation Error of manual in Apache FOP -

[jira] Closed: (DERBY-2932) Connection.createClob() and Connection.createBlob() throw a procedure not found exception and do not switch to non-locator code upon soft upgrade

[ https://issues.apache.org/jira/browse/DERBY-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-2932. - Connection.createClob() and Connection.createBlob() throw a procedure not found exception and do

[jira] Closed: (DERBY-2839) initial problems with the 10.3.1.0 beta candidate

[ https://issues.apache.org/jira/browse/DERBY-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-2839. - initial problems with the 10.3.1.0 beta candidate

[jira] Closed: (DERBY-2896) DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed.

[ https://issues.apache.org/jira/browse/DERBY-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll closed DERBY-2896. - DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818:

Re: Blockers and 10.4

Hi Dyre, These two issues were marked as blockers by the people who logged them. Is that anything more than a statement of how much pain these issues cause those people? If I were to categorize issues according to the severity of their impact, it would look something like this (in declining

[jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

[ https://issues.apache.org/jira/browse/DERBY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559516#action_12559516 ] Jørgen Løland commented on DERBY-3316: -- r612262 | kmarsden | 2008-01-15 23:36:38 +0100

[jira] Closed: (DERBY-716) Re-enable VTIs

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas closed DERBY-716. --- Resolution: Fixed Closing this issue because I've finished the work I planned to do on this and the

[jira] Created: (DERBY-3322) Server guide refers to phantom property in template policy file for the Network Server

Server guide refers to phantom property in template policy file for the Network Server -- Key: DERBY-3322 URL: https://issues.apache.org/jira/browse/DERBY-3322

[jira] Commented: (DERBY-3313) JDBC client driver statement cache

[ https://issues.apache.org/jira/browse/DERBY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559542#action_12559542 ] Kristian Waagan commented on DERBY-3313: At the moment I'm looking into handling of

[jira] Updated: (DERBY-3224) Get Suites.All to run on the phoneME advanced platform

[ https://issues.apache.org/jira/browse/DERBY-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vemund Østgaard updated DERBY-3224: --- Attachment: 3224-diffv2.stat 3224-diffv2 Attaching a new patch for this

Re: Blockers and 10.4

Rick Hillegas wrote: If I were to categorize issues according to the severity of their impact, it would look something like this (in declining order of significance): 1) Engine crashes 2) Data corruption 3) Wrong results 4) Failures (e.g., a query just aborts) 5) Misleading messages, typos,

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

Issue Subscription Filter: Derby: JIRA issues with patch available (12 issues) Subscriber: derby-dev Key Summary DERBY-3254 Implement the replication failover functionality https://issues.apache.org/jira/browse/DERBY-3254 DERBY-3205 Replication: Add connection url command

[jira] Commented: (DERBY-3313) JDBC client driver statement cache

[ https://issues.apache.org/jira/browse/DERBY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559574#action_12559574 ] Bryan Pendleton commented on DERBY-3313: Hi Kristian, thanks for the

[jira] Resolved: (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 resolved DERBY-3023. Resolution: Fixed Fix Version/s: 10.4.0.0 Assignee: A B Derby Info: [Existing Application

Regression Test Report - Daily 612157 - Sun DBTG

[Auto-generated mail] *Daily* 612157/2008-01-15 18:01:04 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0272272 071.70% derbyall F:1,E:01014810147 0 1456.87% suitesAll

[jira] Assigned: (DERBY-3315) Should UCS_BASIC character types have to look at collation elements when dealing with escape character in the LIKE clause?

[ https://issues.apache.org/jira/browse/DERBY-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-3315: -- Assignee: Mamta A. Satoor Should UCS_BASIC character types have to look at collation

[jira] Assigned: (DERBY-2720) remove dead code associated with unsupported National Char implementation

[ https://issues.apache.org/jira/browse/DERBY-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-2720: -- Assignee: Mamta A. Satoor remove dead code associated with unsupported National Char

[jira] Commented: (DERBY-3224) Get Suites.All to run on the phoneME advanced platform

[ https://issues.apache.org/jira/browse/DERBY-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559592#action_12559592 ] Daniel John Debrunner commented on DERBY-3224: -- CallableTest.java - Changed

[jira] Commented: (DERBY-3224) Get Suites.All to run on the phoneME advanced platform

[ https://issues.apache.org/jira/browse/DERBY-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559594#action_12559594 ] Daniel John Debrunner commented on DERBY-3224: -- Or it may require a special

Re: Blockers and 10.4

On 1/16/08, Army [EMAIL PROTECTED] wrote: Rick Hillegas wrote: If I were to categorize issues according to the severity of their impact, it would look something like this (in declining order of significance): 1) Engine crashes 2) Data corruption 3) Wrong results 4) Failures

[jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

[ https://issues.apache.org/jira/browse/DERBY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559596#action_12559596 ] Kathey Marsden commented on DERBY-3316: ---

Re: Blockers and 10.4

Myrna van Lunteren wrote: On 1/16/08, Army [EMAIL PROTECTED] wrote: Rick Hillegas wrote: If I were to categorize issues according to the severity of their impact, it would look something like this (in declining order of significance): 1) Engine crashes 2) Data corruption 3) Wrong

[jira] Commented: (DERBY-3313) JDBC client driver statement cache

[ https://issues.apache.org/jira/browse/DERBY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559609#action_12559609 ] Kristian Waagan commented on DERBY-3313: Bryan wrote: Did I understand correctly

[jira] Resolved: (DERBY-2854) Convert jdbc4/TestResultSetMethods.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-2854. --- Resolution: Fixed Fix Version/s: 10.4.0.0 This was committed with revision

[jira] Resolved: (DERBY-2855) Convert jdbc4/TestConnectionMethods.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren resolved DERBY-2855. --- Resolution: Fixed Fix Version/s: 10.4.0.0 Convert

[jira] Resolved: (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 ] Myrna van Lunteren resolved DERBY-2674. --- Resolution: Fixed I removed the last forgotten file - jdbc40.properties - with

[jira] Commented: (DERBY-3315) Should UCS_BASIC character types have to look at collation elements when dealing with escape character in the LIKE clause?

[ https://issues.apache.org/jira/browse/DERBY-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559617#action_12559617 ] Mamta A. Satoor commented on DERBY-3315: I have removed the code mentioned above

[jira] Commented: (DERBY-2720) remove dead code associated with unsupported National Char implementation

[ https://issues.apache.org/jira/browse/DERBY-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559618#action_12559618 ] Mamta A. Satoor commented on DERBY-2720: I have removed the disabled national

[jira] Commented: (DERBY-2185) Referene manual has conflicting information on when the territory attribute can be specified on the jdbc url.

[ https://issues.apache.org/jira/browse/DERBY-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559621#action_12559621 ] Kim Haase commented on DERBY-2185: -- I agree the two issues are related (and I've marked

[jira] Updated: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3230: -- Derby Info: [Regression] Marking as a regression because this passes with 10.1.3.1 client,

Regression Test Report - tinderbox_trunk16 612506 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 612506/2008-01-16 17:52:17 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0270270 085.87% derbyall F:1,E:01015010149 0

Re: Compatibility issue for 10.4

Thanks to everybody for the discussion so far. And thanks to Martin for revising the SystemPrivilegesBehaviour.html summary attached to DERBY-2109. I think that my initial posting garbled the description of the compatibilty issues. I would like to restate what the backward-compatibility

[jira] Assigned: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-3230: - Assignee: Kathey Marsden Selecting data from a Table raises Error XN008: Query

[jira] Commented: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559662#action_12559662 ] Kathey Marsden commented on DERBY-3230: --- I think this dates back to DERBY-821 when we

[jira] Resolved: (DERBY-2720) remove dead code associated with unsupported National Char implementation

[ https://issues.apache.org/jira/browse/DERBY-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor resolved DERBY-2720. Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.2.2 Merged

[jira] Resolved: (DERBY-3315) Should UCS_BASIC character types have to look at collation elements when dealing with escape character in the LIKE clause?

[ https://issues.apache.org/jira/browse/DERBY-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor resolved DERBY-3315. Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.2.2 Merged

Re: Compatibility issue for 10.4

Rick Hillegas wrote: Thanks to everybody for the discussion so far. And thanks to Martin for revising the SystemPrivilegesBehaviour.html summary attached to DERBY-2109. I think that my initial posting garbled the description of the compatibilty issues. I would like to restate what the

[jira] Commented: (DERBY-2142) NullPointerException while using XAConnection/PooledConnection in a heavily contended multithreaded scenario

[ https://issues.apache.org/jira/browse/DERBY-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559726#action_12559726 ] Kathey Marsden commented on DERBY-2142: --- Asif, do you have a reproduction for this

Regression Test Report - tinderbox_trunk16 612562 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 612562/2008-01-16 21:22:42 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0271271 085.77% derbyall F:13,E:121015010125

[jira] Updated: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3230: -- Attachment: (was: derby-3230_diff.txt) Selecting data from a Table raises Error XN008:

[jira] Updated: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3230: -- Attachment: derby-3230_stat.txt derby-3230_diff.txt Attached is a patch for

[jira] Updated: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3230: -- Attachment: derby-3230_diff.txt Selecting data from a Table raises Error XN008: Query

[jira] Updated: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-3230: -- Derby Info: [Patch Available, Regression] (was: [Regression]) Please review

[jira] Commented: (DERBY-3257) SELECT with HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows - works correctly with 10.2 DB

[ https://issues.apache.org/jira/browse/DERBY-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559758#action_12559758 ] Kathey Marsden commented on DERBY-3257: --- In DERBY-3231, Manish mentioned. Mike, I'll

Reason for errors in the tinderbox test? (Re: svn commit: r612525 [1/2])

Hello, I haven't looked much into this, but I suspect this commit broke several tests. Based on a *very* quick look at the diff only, I think the removal of national character code was a little too broad. For instance, the JDBC layer needs to know about these types to be able to throw

[jira] Commented: (DERBY-3088) convert to junit, or otherwise eliminate version in tests which require an update of the master in the release management process

[ https://issues.apache.org/jira/browse/DERBY-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559792#action_12559792 ] Myrna van Lunteren commented on DERBY-3088: --- Revision 612684 improves the

[jira] Commented: (DERBY-3230) Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server

[ https://issues.apache.org/jira/browse/DERBY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559794#action_12559794 ] Bryan Pendleton commented on DERBY-3230: The change looks solid to me, Kathey. The

feedback on the UserIdentifiers wiki page

A few comments on the wiki page on UserIdentifiers http://wiki.apache.org/db-derby/UserIdentifiers which I found a confusing to read (had to do it 3x). Wanted to check if it's just me. It's the beginning of the document that threw me of track, while the examples at the end help

Re: Reason for errors in the tinderbox test? (Re: svn commit: r612525 [1/2])

I will take a look, Kristian. My apologies if the test failures are caused by my checkin. But I ran derbyall and junit Runall package before checking in and didn't see any errors either on trunk or on 10.3 codeline. Mamta On 1/16/08, Kristian Waagan [EMAIL PROTECTED] wrote: Hello, I haven't

Re: Reason for errors in the tinderbox test? (Re: svn commit: r612525 [1/2])

I think I know what happened. I ran my tests using jdk14 and JDBC4 tests will not run in that framework. Let me try jdk16 to reproduce the failure. It seems test failures are localized in org.apache.derbyTesting.functionTests.tests.jdbc4.SetObjectUnsupportedTest I will take a look and fix the

Regression Test Report - tinderbox_trunk16 612688 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 612688/2008-01-17 04:02:14 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0271271 085.49% derbyall F:13,E:121015010125

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

[ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559833#action_12559833 ] Martin Zaun commented on DERBY-2109: Hi Dan, thanks for the pointer and your comments

[jira] Issue Comment Edited: (DERBY-2109) System privileges

[ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559833#action_12559833 ] mzaun edited comment on DERBY-2109 at 1/16/08 10:57 PM: -- Hi

[jira] Commented: (DERBY-3316) Leak in client if ResultSet not closed

[ https://issues.apache.org/jira/browse/DERBY-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559840#action_12559840 ] Jørgen Løland commented on DERBY-3316: -- Hi Kathey, I reran the tests without getting

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

[ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-3205: - Attachment: startSlave_1d.diff Hi Øystein, Thanks for reviewing the patch. The attached patch