Re: ant all does not pick up modifications in engine/org/apache/derby/iapi/util

Dag H. Wanvik wrote: I changed a file (IdUtil.java) in that directory and noticed it did not get compiled by ant all unless I did a clobber first. Is this a known weakness? Hi Dag, I would say yes. DERBY-2741 is about this issue, but not much information there. -- Kristian Dag

Re: Help ranking applications and last call for Mentors

Kathey Marsden wrote: It would great if some committers could help us rank Google SOC applications. We have a lot of qualified applicants and it is hard to decide. Also having more people ranking will help ensure a higher cumulative score for our students, making it more likely that our

[jira] Closed: (DERBY-3615) Making the instructions more clear in documentation(BUILDING.txt) regarding setting JRE lib path for a Windows system

[ https://issues.apache.org/jira/browse/DERBY-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udai Gupta closed DERBY-3615. - Resolution: Fixed Kathey Marsden has committed this patch... Making the instructions more clear in

Re: ICLA's for students

Hello,Kathey. The icla.pdf downloaded from http://wiki.apache.org/db-derby/DerbyContributorChecklist says,If you have not already done so, please complete and send an original signed Agreement to The Apache Software Foundation, 1901 Munsey Drive, Forest Hill, MD 210502747,U.S.A. If

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588976#action_12588976 ] Knut Anders Hatlen commented on DERBY-3574: --- The committed patch (rev #647931)

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588978#action_12588978 ] Knut Anders Hatlen commented on DERBY-3574: --- Do we really need this extra check

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12588982#action_12588982 ] Tiago R. Espinha commented on DERBY-3574: - If I recall correctly, that check is to

[jira] Updated: (DERBY-3615) Making the instructions more clear in documentation(BUILDING.txt) regarding setting JRE lib path for a Windows system

[ https://issues.apache.org/jira/browse/DERBY-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dyre Tjeldvoll updated DERBY-3615: -- Derby Info: (was: [Patch Available]) Already committed Making the instructions more clear

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589004#action_12589004 ] Knut Anders Hatlen commented on DERBY-3574: --- OK, thanks for the explanation. I

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589009#action_12589009 ] Tiago R. Espinha commented on DERBY-3574: - This is true, I just thought that since

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

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3347: -- Fix Version/s: 10.3.2.2 Merged the fixes to the 10.3 branch and committed revision

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589036#action_12589036 ] Knut Anders Hatlen commented on DERBY-3574: --- It's not a big deal. The extra check

[jira] Commented: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

[ https://issues.apache.org/jira/browse/DERBY-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589063#action_12589063 ] Knut Anders Hatlen commented on DERBY-3616: --- Hi Rick, According to the page you

[jira] Commented: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

[ https://issues.apache.org/jira/browse/DERBY-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589059#action_12589059 ] Rick Hillegas commented on DERBY-3616: -- Thanks for the quick review, Knut. I agree

[jira] Commented: (DERBY-3397) Derby 10.3.1.4 and 10.3.2.1 break scrollable result sets? Hibernate Query.setFirstResult and/or setMaxResults

[ https://issues.apache.org/jira/browse/DERBY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589068#action_12589068 ] martin kovacik commented on DERBY-3397: --- I can confirm this bug. I use Derby

[jira] Commented: (DERBY-3397) Derby 10.3.1.4 and 10.3.2.1 break scrollable result sets? Hibernate Query.setFirstResult and/or setMaxResults

[ https://issues.apache.org/jira/browse/DERBY-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589069#action_12589069 ] Michael Lossos commented on DERBY-3397: --- I was also using the EmbeddedDriver when I

[jira] Created: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner

Implement more load types for org.apache.derbyTesting.perf.clients.Runner - Key: DERBY-3619 URL: https://issues.apache.org/jira/browse/DERBY-3619 Project: Derby Issue

[jira] Commented: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

[ https://issues.apache.org/jira/browse/DERBY-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589071#action_12589071 ] Rick Hillegas commented on DERBY-3616: -- Thanks for continuing to look into this, Knut.

[jira] Commented: (DERBY-3431) DatabaseMetaData.getConnection returns the wrong connection when using connection pooling

[ https://issues.apache.org/jira/browse/DERBY-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589081#action_12589081 ] Kristian Waagan commented on DERBY-3431: Was the previous comment meant for

Re: Are there any unit tests for the CacheManager/ Concurrent cache

Kathey Marsden [EMAIL PROTECTED] writes: I am interested in stressing the concurrent cache to debug a possible jvm issue and was wondering if there are already any existing unit tests or if anyone has ideas about setting them up. Hi Kathey, The only test I know about that tests the

another release candidate?

I have just patched 10.4 to handle DERBY-3616. That bug turns out to be a fairly disabling problem for Table Functions. Because of DERBY-3616, Table Functions may or may not be usable on a given platform, depending on the platform's default string encoding. In particular, Table Functions

Re: ICLA's for students

Junjie Peng wrote: Hello,Kathey. The icla.pdf downloaded from http://wiki.apache.org/db-derby/DerbyContributorChecklist says,If you have not already done so, please complete and send an original signed Agreement to The Apache Software Foundation, 1901 Munsey Drive, Forest Hill, MD

buddy testing of 10.4

So far, there isn't much evidence that 10.4 is being buddy-tested. I have added a table of features to the buddy-testing page: http://wiki.apache.org/db-derby/TenFourBuddyTesting It would be good to at least verify that behavior and documentation agree with one another. Thanks, -Rick

[jira] Updated: (DERBY-3581) Changing certain properties on client DataSource objects causes existing connections to reflect the new values

[ https://issues.apache.org/jira/browse/DERBY-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3581: --- Derby Info: (was: [Patch Available]) Committed

Re: ICLA's for students

Jean T. Anderson wrote: 1. What's the deadline we submit our CLAs? You should file a ICLA before you contribute a significant patch. For a small patch, just granting license to Apache in Jira is probably ok. Kathey

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

Issue Subscription Filter: Derby: JIRA issues with patch available (2 issues) Subscriber: derby-dev Key Summary DERBY-3409 Remove JDBC 2.0-specific topics from Reference Manual and merge implementation notes as needed https://issues.apache.org/jira/browse/DERBY-3409

[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner

[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589128#action_12589128 ] Kathey Marsden commented on DERBY-3619: --- It would be good to have a performance

Regression Test Report - Daily 647871 - Sun DBTG

[Auto-generated mail] *Daily* 647871/2008-04-14 18:01:07 MEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1269268 083.04% derbyall 098819881 0 1297.89% suitesAll sles 0

Re: [jira] Updated: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

Knut's suggestions seems good. Also whatever we decide it would be nice to get this right in the 10.4 release to avoid any upgrade issues with changing the format in the future. /mikem Knut Anders Hatlen (JIRA) wrote: [

[jira] Created: (DERBY-3620) Problem with Derby on Windows 2008

Problem with Derby on Windows 2008 -- Key: DERBY-3620 URL: https://issues.apache.org/jira/browse/DERBY-3620 Project: Derby Issue Type: Bug Components: Network Client, Network Server Affects

Re: [jira] Updated: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

Thanks, Mike. I don't think I understand what the upgrade issues are. Could you explain? Regards, -Rick Mike Matrigali wrote: Knut's suggestions seems good. Also whatever we decide it would be nice to get this right in the 10.4 release to avoid any upgrade issues with changing the format

running unit tests on IBM Java 6 on Ubuntu 7

I am trying to run unit tests on the IBM Java 6 platform on Ubuntu 7. I notice that this combination is not recorded in our list of known good platforms: http://wiki.apache.org/db-derby/PlatformTestsDerby However, I suspect that that page is not kept up-to-date and someone is probably

[jira] Created: (DERBY-3621) Hibernate. Derby uses type 'text' as clob(255) instead of long varchar

Hibernate. Derby uses type 'text' as clob(255) instead of long varchar -- Key: DERBY-3621 URL: https://issues.apache.org/jira/browse/DERBY-3621 Project: Derby Issue Type:

Re: running unit tests on IBM Java 6 on Ubuntu 7

I didn't do the test with Ubuntu, but is it because of DERBY-3545? -Manjula On 4/15/08, Rick Hillegas [EMAIL PROTECTED] wrote: I am trying to run unit tests on the IBM Java 6 platform on Ubuntu 7. I notice that this combination is not recorded in our list of known good platforms:

Re: running unit tests on IBM Java 6 on Ubuntu 7

On 4/15/08, Rick Hillegas [EMAIL PROTECTED] wrote: I am trying to run unit tests on the IBM Java 6 platform on Ubuntu 7. I notice that this combination is not recorded in our list of known good platforms: http://wiki.apache.org/db-derby/PlatformTestsDerby However, I suspect that that page is

[jira] Commented: (DERBY-3621) Hibernate. Derby uses type 'text' as clob(255) instead of long varchar

[ https://issues.apache.org/jira/browse/DERBY-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589183#action_12589183 ] Thomas Nielsen commented on DERBY-3621: --- Based on your original email[1] to

Re: running unit tests on IBM Java 6 on Ubuntu 7

Myrna van Lunteren wrote: On 4/15/08, Rick Hillegas [EMAIL PROTECTED] wrote: I am trying to run unit tests on the IBM Java 6 platform on Ubuntu 7. I notice that this combination is not recorded in our list of known good platforms: http://wiki.apache.org/db-derby/PlatformTestsDerby However, I

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

[ https://issues.apache.org/jira/browse/DERBY-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suran Jayathilaka updated DERBY-3587: - Attachment: jdbcapi-testRelative-converted-2.diff Thanks for the helpful comments. This

Re: [jira] Created: (DERBY-3620) Problem with Derby on Windows 2008

fyi - The machine is IPv6 and Eric will be redoing the test with the recommneded JVM settings for dual stack machines. Eric Kirchstein (JIRA) wrote: Problem with Derby on Windows 2008 -- Key: DERBY-3620 URL:

[jira] Created: (DERBY-3622) SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE needs a better description in the reference manual

SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE needs a better description in the reference manual - Key: DERBY-3622 URL: https://issues.apache.org/jira/browse/DERBY-3622

[jira] Commented: (DERBY-3568) Convert jdbcapi/savepointJdbc30_JSR169.java and jdbcapi/savepointJdbc30_XA.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589225#action_12589225 ] Myrna van Lunteren commented on DERBY-3568: --- some minor comments: - there are

Re: running unit tests on IBM Java 6 on Ubuntu 7

Rick Hillegas wrote: Myrna van Lunteren wrote: On 4/15/08, Rick Hillegas [EMAIL PROTECTED] wrote: I am trying to run unit tests on the IBM Java 6 platform on Ubuntu 7. I notice that this combination is not recorded in our list of known good platforms:

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

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha resolved DERBY-3574. - Resolution: Fixed Fix Version/s: 10.5.0.0 Issue resolved. Final revision

[jira] Resolved: (DERBY-3545) NullPointerException in TableFunctionTest.noSpecialCollation and specialCollation

[ https://issues.apache.org/jira/browse/DERBY-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-3545. -- Resolution: Fixed NullPointerException in TableFunctionTest.noSpecialCollation and

[jira] Assigned: (DERBY-3623) Convert deadlockMode.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha reassigned DERBY-3623: --- Assignee: Tiago R. Espinha Convert deadlockMode.java to JUnit

[jira] Created: (DERBY-3623) Convert deadlockMode.java to JUnit

Convert deadlockMode.java to JUnit -- Key: DERBY-3623 URL: https://issues.apache.org/jira/browse/DERBY-3623 Project: Derby Issue Type: Task Components: Test Reporter: Tiago R. Espinha

[jira] Commented: (DERBY-3568) Convert jdbcapi/savepointJdbc30_JSR169.java and jdbcapi/savepointJdbc30_XA.java to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589236#action_12589236 ] Myrna van Lunteren commented on DERBY-3568: --- I removed those references with

[jira] Updated: (DERBY-3624) testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing

[ https://issues.apache.org/jira/browse/DERBY-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-3624: -- Attachment: st_derby715.tmp derby.log attaching derby.log found after

[jira] Created: (DERBY-3624) testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing

testfailure in storetests/st_derby715 with ibm 1.5 on iseries machine; one deadlock message missing --- Key: DERBY-3624 URL:

[jira] Commented: (DERBY-2901) convert lang/concateTests to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589263#action_12589263 ] Myrna van Lunteren commented on DERBY-2901: --- I have not seen any recent activity

[jira] Created: (DERBY-3625) XSDA3 error in concateTests in lang.LangHarnessJavaTest

XSDA3 error in concateTests in lang.LangHarnessJavaTest Key: DERBY-3625 URL: https://issues.apache.org/jira/browse/DERBY-3625 Project: Derby Issue Type: Bug Components:

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

[ https://issues.apache.org/jira/browse/DERBY-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-3347: -- Trying to figure out what to tell 10.3 users that may have hit this. Does anyone have a db that

[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: --- Attachment: DERBY-3542-1.diff DERBY-3542-1.stat Dyre Tjeldvoll wrote: I definitely

Re: [jira] Updated: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

Rick Hillegas wrote: Thanks, Mike. I don't think I understand what the upgrade issues are. Could you explain? Regards, -Rick I may just have jumped in too soon, as I don't really understand what the encoding that was a problem is actually doing. I was just working off the info in the bug

[jira] Created: (DERBY-3626) Issue with bracketed SQL comments on a remote database connection from ij

Issue with bracketed SQL comments on a remote database connection from ij - Key: DERBY-3626 URL: https://issues.apache.org/jira/browse/DERBY-3626 Project: Derby Issue

[jira] Updated: (DERBY-3626) Issue with bracketed SQL comments on a remote database connection from ij

[ https://issues.apache.org/jira/browse/DERBY-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Zaun updated DERBY-3626: --- Attachment: comments_test_ok.sql comments_test_fail.sql Attached SQL queries from

Re: [jira] Updated: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

Mike Matrigali wrote: Rick Hillegas wrote: Thanks, Mike. I don't think I understand what the upgrade issues are. Could you explain? Regards, -Rick I may just have jumped in too soon, as I don't really understand what the encoding that was a problem is actually doing. I was just working

[jira] Commented: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

[ https://issues.apache.org/jira/browse/DERBY-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589378#action_12589378 ] Bryan Pendleton commented on DERBY-3616: The patch to the trunk resolves the

[jira] Created: (DERBY-3627) derbynet/DerbyNetAutoStart.java with DerbyNetClient fails intermittently on iseries

derbynet/DerbyNetAutoStart.java with DerbyNetClient fails intermittently on iseries --- Key: DERBY-3627 URL: https://issues.apache.org/jira/browse/DERBY-3627 Project:

[jira] Updated: (DERBY-3627) derbynet/DerbyNetAutoStart.java with DerbyNetClient fails intermittently on iseries

[ https://issues.apache.org/jira/browse/DERBY-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-3627: -- Attachment: DerbyNetAutoStart.diff DerbyNetAutoStart.out

[jira] Updated: (DERBY-3627) derbynet/DerbyNetAutoStart.java with DerbyNetClient fails intermittently on iseries

[ https://issues.apache.org/jira/browse/DERBY-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren updated DERBY-3627: -- Attachment: derbynet.log derby.log Attaching all files that may have

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

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-3603: --- Attachment: updateSubqueryMaster.diff Thanks Army for the clear and detailed description of

Re: ICLA's for students

Thanks to Jean and Kathey. I got it! Regards Junjie

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

[ https://issues.apache.org/jira/browse/DERBY-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589397#action_12589397 ] Bryan Pendleton commented on DERBY-3603: Committed the change to the trunk as