[jira] Commented: (DERBY-2316) Convert compatibility/testScript.xml to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485096 ] Ole Solberg commented on DERBY-2316: Thanks for reviewing and committing Rick! I will follow up your suggestions

Regression Test Report - tinderbox_trunk16 523528 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 523528/2007-03-29 03:42:38 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0373373 0 211.97% derbyall F:0,E:172557254 0

Re: Collation feature discussion

I think I have been able to interpret SQL spec for collation type of string literal. Let me know if that interpretation sounds correct. I am copying some of the relevant infromation about collation from earlier mail, so everything related to collation type determination is in one central place an

[jira] Closed: (DERBY-2491) Convert distinct.sql to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew McIntyre closed DERBY-2491. -- Resolution: Fixed Fix Version/s: 10.3.0.0 Committed new test to repository with revision

Regression Test Report - tinderbox_trunk16 523476 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 523476/2007-03-29 00:02:45 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0373373 0 100.31% derbyall F:0,E:172557254 0

[jira] Reopened: (DERBY-1496) testSecMec needs many masters - should convert to junit

[ https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner reopened DERBY-1496: -- NSSecurityMechanismTest has this TODO in it: // TODO: sleep ridiculous

[jira] Commented: (DERBY-2488) When loaded by jvm1.6 - Derby JDBC 3.0 driver returns 4 for JDBC driver major

[ https://issues.apache.org/jira/browse/DERBY-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485033 ] Daniel John Debrunner commented on DERBY-2488: -- No, there are two data sources versions, the 40 ones and

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

Andrew McIntyre (JIRA) wrote: and since all the tests pass with or without ruleBasedOptimization set to true, I'll leave that off. Not really worth investigating, since it seems to have no effect on the new test. Unless of course setting that property to true revealed an error once upon a t

[jira] Assigned: (DERBY-2500) Assertion failure preparing query with AND and OR in where clause

[ https://issues.apache.org/jira/browse/DERBY-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B reassigned DERBY-2500: -- Assignee: A B > Assertion failure preparing query with AND and OR in where clause > ---

[jira] Commented: (DERBY-2316) Convert compatibility/testScript.xml to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485029 ] Rick Hillegas commented on DERBY-2316: -- Thanks for this improvement, Ole! Replacing the compatibiltiy driver wit

[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_12485028 ] Andrew McIntyre commented on DERBY-47: -- Army> Note though that this is an actual engine bug, not just a test probl

[jira] Created: (DERBY-2500) Assertion failure preparing query with AND and OR in where clause

Assertion failure preparing query with AND and OR in where clause - Key: DERBY-2500 URL: https://issues.apache.org/jira/browse/DERBY-2500 Project: Derby Issue Type: Bug

[jira] Commented: (DERBY-2488) When loaded by jvm1.6 - Derby JDBC 3.0 driver returns 4 for JDBC driver major

[ https://issues.apache.org/jira/browse/DERBY-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485010 ] Stan Bradbury commented on DERBY-2488: -- Thanks, Dan, for the information. I realized the results of this test c

[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_12485008 ] A B commented on DERBY-47: -- > 1. shall I open a new issue for the test failure? Yes, I think that'd be good. Note though tha

Regression Test Report - tinderbox_trunk16 523429 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 523429/2007-03-28 20:12:45 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0373373 0 100.79% derbyall F:0,E:172557254 0

[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_12485002 ] Andrew McIntyre commented on DERBY-47: -- Hah! I had already deleted all the properties files for the old tests in m

[jira] Commented: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ https://issues.apache.org/jira/browse/DERBY-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484998 ] Suresh Thalamati commented on DERBY-700: Thanks a lot for summarizing the problems and possible solutions for

[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_12484994 ] A B commented on DERBY-47: -- Hi Andrew, Thank you for reporting this! My guess is that the difference between the JUnit test

[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_12484985 ] Andrew McIntyre commented on DERBY-47: -- Hi Army, I just checked in a converted JUnit test for the old distinct.sql

[jira] Commented: (DERBY-2476) convert lang/forbitdata.java test to junit test

[ https://issues.apache.org/jira/browse/DERBY-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484984 ] Andrew McIntyre commented on DERBY-2476: The new test looks good, one minor comment: Instead of putting hand

Re: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

Jeffrey Clary wrote: Unfortunately, as a new Derby contributor, I am still working the kinks out of my building and testing. I haven't been able to get a clean baseline test for derbyall, and I haven't tried suites.All. I'll get to that eventually, but maybe in the meantime a submitter will

Regression Test Report - tinderbox_trunk16 523340 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 523340/2007-03-28 16:22:39 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0373373 0 101.18% derbyall F:0,E:172557254 0

RE: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

Unfortunately, as a new Derby contributor, I am still working the kinks out of my building and testing. I haven't been able to get a clean baseline test for derbyall, and I haven't tried suites.All. I'll get to that eventually, but maybe in the meantime a submitter will see in JIRA that you ra

[jira] Commented: (DERBY-2490) Clarify transaction management in LanguageConnectionContext.

[ https://issues.apache.org/jira/browse/DERBY-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484942 ] Daniel John Debrunner commented on DERBY-2490: -- Thanks Mike, I think this info is essential to add to ja

[jira] Commented: (DERBY-2489) Document the policy-reloading system procedure.

[ https://issues.apache.org/jira/browse/DERBY-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484941 ] Kim Haase commented on DERBY-2489: -- Thanks for this excellent documentation, Rick. Just a few doc nits: cdevbabejg

[jira] Assigned: (DERBY-2499) Update Tuning Guide documentation to reflect the new static IN list transformation that occurs as a result of DERBY-47.

[ https://issues.apache.org/jira/browse/DERBY-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart reassigned DERBY-2499: Assignee: Laura Stewart > Update Tuning Guide documentation to reflect the new static IN li

[jira] Commented: (DERBY-2498) NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was invalid

[ https://issues.apache.org/jira/browse/DERBY-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484928 ] Myrna van Lunteren commented on DERBY-2498: --- ClientConnectionPoolDataSource also gives a NPE if the databas

[jira] Commented: (DERBY-2493) Use unsynchronized collections in BackingStoreHashtable

[ https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484923 ] Andrew McIntyre commented on DERBY-2493: Thanks for the review, Knut! I appreciate it. checkDistinctRows doe

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

Laura Stewart (JIRA) wrote: In the Tuning Guide, the IN operator is mentioned in the optimization and query sections, as shown below: Thank you, Laura. I filed DERBY-2499 for documentation of the new IN list behavior. I'll try to look into this sometime in the near future... Army

[jira] Created: (DERBY-2499) Update Tuning Guide documentation to reflect the new static IN list transformation that occurs as a result of DERBY-47.

Update Tuning Guide documentation to reflect the new static IN list transformation that occurs as a result of DERBY-47. --- Key: DERBY-2499 URL: ht

[jira] Resolved: (DERBY-2256) Wrong Results: Use of decimal values in an IN-list with INTEGER left operand can lead to extra rows.

[ https://issues.apache.org/jira/browse/DERBY-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B resolved DERBY-2256. Resolution: Fixed Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Thank you very much

Re: [jira] Commented: (DERBY-2493) Use unsynchronized collections in BackingStoreHashtable

it depends on what the test is testing, but I usually consider these ordering dependencies a test bug - ie. they are counting on an order not specified by SQL. For .sql tests there are usually 2 possible fixes: 1) If what is being tested is not affected by adding an order by to the query, I j

[jira] Updated: (DERBY-1949) locate function returns invalid value when first parameter is empty string

[ https://issues.apache.org/jira/browse/DERBY-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-1949: --- Attachment: rrefsqlj61998.html docs_v2.diff Thanks Oleksandr for the review a

[jira] Commented: (DERBY-2491) Convert distinct.sql to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484926 ] Andrew McIntyre commented on DERBY-2491: Whoops! Meant to attach my response to the review comments to this i

[jira] Updated: (DERBY-2490) Clarify transaction management in LanguageConnectionContext.

[ https://issues.apache.org/jira/browse/DERBY-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2490: -- The best info for store provided nested info should be in the iapi javadoc where you get the neste

[jira] Updated: (DERBY-2466) Allow dynamic reloading of the security policy file

[ https://issues.apache.org/jira/browse/DERBY-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-2466: - Attachment: derby-2466-04.diff Committed derby-2466-04.diff at subversion revision 523399.. This

[jira] Created: (DERBY-2498) NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was invalid

NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was invalid - Key: DERBY-2498 URL: https://issues.apache.org/jira/browse/DERBY-2498

Re: Question about MultiProbeTableScanResultSet.probeValues[]

[EMAIL PROTECTED] wrote: when looking at the code it seems to me that the probe values are set by the constructor, and then cloned on each new openCore(). I don't think this approach is compatible with re-using internal result sets (see DERBY-827), because when re-executing a prepared statement

[jira] Created: (DERBY-2497) convert lang/coalesceTests.java to junit

convert lang/coalesceTests.java to junit Key: DERBY-2497 URL: https://issues.apache.org/jira/browse/DERBY-2497 Project: Derby Issue Type: Test Components: Test Reporter: Ramandee

Regression Test Report - Daily 522555S1 - Sun DBTG

[Auto-generated mail] *Daily* 522555S1/2007-03-26 18:00:10 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin NA NA NANA derbyall NA NA NANA suitesAll sles NA

[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-1949 locate function returns invalid value when first parameter is empty string https://issues.apache.org/jira/browse/DERBY-1949 DERBY-2467 Convert lang/up

Re: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

Jeffrey Clary wrote: Thanks for the review. This is the first time I have contributed any code (one line ;-) to Derby. At this point will the fix be picked up by a submitter or is there something else I need to do to make sure it gets into the next release? I see that you have set the "Patc

[jira] Commented: (DERBY-1934) Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions

[ https://issues.apache.org/jira/browse/DERBY-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484905 ] Kim Haase commented on DERBY-1934: -- Uh-oh, we've got colliding JIRAs. DERBY-2090 (fixed recently) was actually a du

Re: Any fix release planned before 10.3?

Jeffrey Clary wrote: I’ve been reading at thread on this list discussing a 10.3 release candidate in early May. Are there any 10.2.x fix releases planned between now and then? Thanks, Jeff Hi Jeff, No one has suggested this yet. My gut feeling is that we will feel pressure to produce a

Regression Test Report - tinderbox_trunk16 523256 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 523256/2007-03-28 12:02:30 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0373373 0 100.78% derbyall F:0,E:172557254 0

Any fix release planned before 10.3?

I've been reading at thread on this list discussing a 10.3 release candidate in early May. Are there any 10.2.x fix releases planned between now and then? Thanks, Jeff

RE: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

Thanks for the review. This is the first time I have contributed any code (one line ;-) to Derby. At this point will the fix be picked up by a submitter or is there something else I need to do to make sure it gets into the next release? -Original Message- From: John H. Embretsen (JIRA

[jira] Commented: (DERBY-2491) Convert distinct.sql to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484868 ] Knut Anders Hatlen commented on DERBY-2491: --- If I have read the patch correctly, DistinctTest.checkDistinct

[jira] Assigned: (DERBY-2432) Implement a transaction time out for XA transactions

[ https://issues.apache.org/jira/browse/DERBY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julius Stroffek reassigned DERBY-2432: -- Assignee: Julius Stroffek > Implement a transaction time out for XA transactions >

[jira] Commented: (DERBY-2493) Use unsynchronized collections in BackingStoreHashtable

[ https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484860 ] Knut Anders Hatlen commented on DERBY-2493: --- It seems like the ordering is already a problem in lang/distin

[jira] Commented: (DERBY-2493) Use unsynchronized collections in BackingStoreHashtable

[ https://issues.apache.org/jira/browse/DERBY-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484857 ] Knut Anders Hatlen commented on DERBY-2493: --- Replacing the Hashtable with a HashMap was trivial, but becaus

[jira] Commented: (DERBY-1017) locking issue with a select statement using an order by clause

[ https://issues.apache.org/jira/browse/DERBY-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484836 ] Peter Nedonosko commented on DERBY-1017: Hi, I work on a next version of the eXo JCR product (eXo Platform).

[jira] Created: (DERBY-2496) Implement Blob support for Locators

Implement Blob support for Locators --- Key: DERBY-2496 URL: https://issues.apache.org/jira/browse/DERBY-2496 Project: Derby Issue Type: Sub-task Reporter: Øystein Grøvlen DERBY-2347 adds the pos

[jira] Commented: (DERBY-1949) locate function returns invalid value when first parameter is empty string

[ https://issues.apache.org/jira/browse/DERBY-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484820 ] Oleksandr Alesinskyy commented on DERBY-1949: - Yes, I definitely had misread the documentation. While it

[jira] Created: (DERBY-2495) Create framework for calling locator related stored procedures from client

Create framework for calling locator related stored procedures from client -- Key: DERBY-2495 URL: https://issues.apache.org/jira/browse/DERBY-2495 Project: Derby Issue

[jira] Commented: (DERBY-2467) Convert lang/updateCursor.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484795 ] Andrew McIntyre commented on DERBY-2467: Ugo> I think that the issue is almost resolved. The only thing that

[jira] Commented: (DERBY-1949) locate function returns invalid value when first parameter is empty string

[ https://issues.apache.org/jira/browse/DERBY-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484790 ] Kristian Waagan commented on DERBY-1949: In a patch I recently reviewed: if (searchStr == "")

[jira] Commented: (DERBY-2460) Create a framework for writing unit tests that will access a private fields of derby classes.

[ https://issues.apache.org/jira/browse/DERBY-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484789 ] Julius Stroffek commented on DERBY-2460: I only thought that if we do thinks like running tests from classes

[jira] Commented: (DERBY-827) Performance can be improved by re-using language ResultSets across Activation executions.

[ https://issues.apache.org/jira/browse/DERBY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484782 ] Dyre Tjeldvoll commented on DERBY-827: -- Thanks for the feedback AB. Here are some answers: AB> If so, could we r

Re: Running test suites and interpreting results

On 3/27/07, Jeffrey Clary <[EMAIL PROTECTED]> wrote: I didn't attach them before because of their size, but here you go. A few questions: - it appears you are building 10.2.2.0 here. 10.2.2.0 still supports JDK 1.3.1 and requires a set of 1.3.1 runtime classes be available and that j13lib in y

new explain functions

Hi Derby community! There is a patch for new explain functions. Please inspect the JIRA Issue Derby-2487 to see the XPLAIN extensions. I hope the attached documents answer all arising questions. Is it okay to attach a zip file version of the demo application to the JIRA issue? I want to get some

[jira] Commented: (DERBY-2487) Enhance Derby with EXPLAIN Functionality

[ https://issues.apache.org/jira/browse/DERBY-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484770 ] Felix Beyer commented on DERBY-2487: note to answer of question 1) The UUID is hold in the stmt_id attribute o ft

[jira] Commented: (DERBY-2487) Enhance Derby with EXPLAIN Functionality

[ https://issues.apache.org/jira/browse/DERBY-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484764 ] Felix Beyer commented on DERBY-2487: >Why did you choose to spell "explain" without the "e" in the code? There`s

Question about MultiProbeTableScanResultSet.probeValues[]

Hi, when looking at the code it seems to me that the probe values are set by the constructor, and then cloned on each new openCore(). I don't think this approach is compatible with re-using internal result sets (see DERBY-827), because when re-executing a prepared statement with different paramete

[jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent database

[ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484757 ] John H. Embretsen commented on DERBY-2480: -- I tried the patch, DERBY-2480-1.diff, and it seems to fix this i

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

On Tue, Mar 27, 2007 at 02:55:13PM -0700, Ramandeep Kaur wrote: > Hi Ugo, > > I saw you have opened DERBY-2467 to convert lang/updateCursor.java to JUnit. > Actually as you did not add information on > *http://wiki.apache.org/db-derby/LangJunitTestConversion > *