Re: DERBY_INSTALL and DERBY_HOME

On 6/15/06, Jean T. Anderson [EMAIL PROTECTED] wrote: Jean T. Anderson wrote: DERBY_INSTALL is what has been in place. If I remember right, DERBY_HOME was to be introduced in 10.2 to conform to the usage of other Apache projects. And I bet there's even a Jira issue for that ... I'll post a

[jira] Commented: (DERBY-1032) Create new scripts which follow common practice at Apache

[ http://issues.apache.org/jira/browse/DERBY-1032?page=comments#action_12416463 ] Andrew McIntyre commented on DERBY-1032: For this change, I propose the following: * create new scripts which replicate the functionality provided by the scripts in

[jira] Assigned: (DERBY-1064) Delete cascade causes NULL values inserted into table when after delete Trigger fires

[ http://issues.apache.org/jira/browse/DERBY-1064?page=all ] Fernanda Pizzorno reassigned DERBY-1064: Assign To: Fernanda Pizzorno Delete cascade causes NULL values inserted into table when after delete Trigger fires

Re: Did the MessageBundleTest pass before it was made part of derbyall?

On 6/15/06, David Van Couvering [EMAIL PROTECTED] wrote: I ran derbyall on my machine prior to checkin and it worked. But this checkin was the first time derbyall included MessageBundleTest. It did not pass before then. I must have not properly checked in the output file, is all I can think

Regression Test Failure! - Derby 414643 - Sun DBTG

[Auto-generated mail] *Derby* 414643/2006-06-15 19:46:09 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 16713697 0 115.76% SunOS-5.10_i86pc-i386 Details in

[jira] Resolved: (DERBY-1388) Integrate processing code of two writeScalarStream methods.

[ http://issues.apache.org/jira/browse/DERBY-1388?page=all ] Tomohito Nakayama resolved DERBY-1388: -- Resolution: Fixed Integrate processing code of two writeScalarStream methods. ---

[jira] Resolved: (DERBY-501) Client and embedded drivers differ on invoking a procedure that returns a single Dynamic resultSet using CallableStatement.executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-501?page=all ] Knut Anders Hatlen resolved DERBY-501: -- Fix Version: 10.2.0.0 Resolution: Fixed Committed revision 414795. Client and embedded drivers differ on invoking a procedure that

Regression Test Failure! - TinderBox_Derby 414797 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 414797/2006-06-16 12:22:27 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1676675 2 142.82% SunOS-5.10_i86pc-i386 Details in

Copyrights redux

Hi Jean, I wanted to confirm with you what we should do about copyright notices. Copyright notices seem to appear in three places: 1) On the Derby website 2) In the published user guides which we bundle with releases 3) In the Derby source code, including the source code for the web site

Re: Copyrights redux

Hi Jean, While I'm on the topic: I asked these questions in the context of 10.2, but it seems that issue (2) may apply to 10.1.3 as well. Do the copyright notices for the 10.1.3 release need to conform to the pattern in (2)? Thanks, -Rick Rick Hillegas wrote: Hi Jean, I wanted to

[jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12416494 ] John H. Embretsen commented on DERBY-1326: -- Deepa Remesh commented: --- [snip] From current behaviour, we do not shutdown network server

[jira] Updated: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Ole Solberg updated DERBY-989: -- Attachment: 989-411220-derbyall_derbyall_unit_unit_derby.log Mike Matrigali wrote: Re: are actual result files for sun's DBTG test runs kept around? I am looking

[jira] Updated: (DERBY-920) small delta's to replace cloudscape etc with derby in comments/code

[ http://issues.apache.org/jira/browse/DERBY-920?page=all ] Bryan Pendleton updated DERBY-920: -- Derby Info: (was: [Patch Available]) small delta's to replace cloudscape etc with derby in comments/code

[jira] Resolved: (DERBY-920) small delta's to replace cloudscape etc with derby in comments/code

[ http://issues.apache.org/jira/browse/DERBY-920?page=all ] Bryan Pendleton resolved DERBY-920: --- Fix Version: 10.2.0.0 Resolution: Fixed Committed to subversion as revision 414832. http://svn.apache.org/viewcvs?rev=414832view=rev Thanks

[jira] Commented: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=comments#action_12416518 ] Knut Anders Hatlen commented on DERBY-137: -- I have (or more precisely, a test program of mine has) gone through all the DatabaseMetaData methods and compared them to

[jira] Created: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE -- Key: DERBY-1421 URL: http://issues.apache.org/jira/browse/DERBY-1421 Project: Derby Type: Bug

[jira] Updated: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1421?page=all ] V.Narayanan updated DERBY-1421: --- Attachment: TestUpdateBinaryStream.java The above program fails with the following message Exception in thread main

[jira] Assigned: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1421?page=all ] Fernanda Pizzorno reassigned DERBY-1421: Assign To: Fernanda Pizzorno ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

Possible CPU loop in testProtocol in cross-release scenario?

I was trying to verify that the changes in DERBY-920 hadn't introduced any new compatibility problems (they shouldn't, because we were changing an internal class, but I wanted to make sure). So I was trying to follow some old tips about how to run tests with an old client against a new server,

Re: [jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

John H. Embretsen (JIRA) wrote: I don't know if this is very helpful with regards to this Jira issue. Thanks, John; this is definitely helpful. I'm a little worried that DERBY-1326 and DERBY-51 are getting inter-twined, though; it seems like your comments are very applicable to DERBY-51. I

[jira] Resolved: (DERBY-1392) Corner case behaviour in RAFContainer#writePage() can cause invalid data to be written to data files

[ http://issues.apache.org/jira/browse/DERBY-1392?page=all ] Mike Matrigali resolved DERBY-1392: --- Fix Version: 10.1.3.1 Resolution: Fixed I merged/resolved conflicts from this change in the trunk to the 10.1 branch and committed as follows:

[jira] Updated: (DERBY-1413) SQL State STORE_XA_XAER_DUPID does not have a matching message

[ http://issues.apache.org/jira/browse/DERBY-1413?page=all ] Mike Matrigali updated DERBY-1413: -- Assign To: (was: Mike Matrigali) As described above I looked at creating a message for this, but my take is that one exists. I am taking myself off

Re: [jira] Commented: (DERBY-1397) Tuning Guide: Puzzling optimizer documentation

Bryan Pendleton wrote: Is it really realistic, though, to allow a setting of 2 million, which gives the optimizer permission to try to create a in-memory hash table of 2 gigabytes? I mean, I'd need a 64-bit JVM... Related, is it worth putting a line or two in this doc telling the user that it

Regression Test Failure! - TinderBox_Derby 414832 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 414832/2006-06-16 16:02:27 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1676675 2 144.76% SunOS-5.10_i86pc-i386 Details in

Re: Copyrights redux

Hi, Rick I'd like to redo your list in terms of (1) internal for source code vs. (2) externally viewable because the new changes just affect the first. 1) Internal for source code : due date 8/1/06 for releases This is a new policy that takes effect for releases starting Aug 1. It doesn't

[jira] Created: (DERBY-1422) Derby web site source needs headers that comply with new ASF policy

Derby web site source needs headers that comply with new ASF policy --- Key: DERBY-1422 URL: http://issues.apache.org/jira/browse/DERBY-1422 Project: Derby Type: Sub-task Components: Web Site

Re: [jira] Commented: (DERBY-1326) Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client

Bryan Pendleton wrote: I'm a little worried that DERBY-1326 and DERBY-51 are getting inter-twined, though; it seems like your comments are very applicable to DERBY-51. Yes, the two issues are definitely related. However, let me point out that DERBY-51 is about what happens to Derby embedded

[jira] Updated: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=all ] Kathey Marsden updated DERBY-930: - Derby Info: [Existing Application Impact, Release Note Needed] This change may impact existing applications as evidenced by the need to change a related

[jira] Reopened: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=all ] Kathey Marsden reopened DERBY-930: -- Reopened because at least release note is needed for behavior change. Add support for autoloading of Derby client drivers

[jira] Commented: (DERBY-1399) DerbyNetAutoStart test fails on JDK 1.6 after introduction JDBC4 driver autoloading

[ http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416568 ] Kathey Marsden commented on DERBY-1399: --- Thanks Olav. I reopened DERBY-930 so a release note can be added descibing the user impact and describe symptoms users might

Apache Derby (in the guise of Java DB) now shipping in Sun Java SE JDK

As you may or may not have seen on the blogosphere, build 88 of Mustang includes Java DB 10.2, Sun's supported distribution of Derby 10.2. This is great news, both for our team and for developers. Developers get the Best Database In the World (TM) out-of-the box, and Derby will likely get a

[jira] Commented: (DERBY-1394) Working With Derby - Introduction and prerequisites - Improvements

[ http://issues.apache.org/jira/browse/DERBY-1394?page=comments#action_12416577 ] Stan Bradbury commented on DERBY-1394: -- Thanks, Halley, for all the attention you are giving to improving Working With Derby. I like your suggestions and think we

ApacheCon Asia: August 15-17, 2006, in Sri Lanka

The call for papers is open and the deadline for submissions is July 9: http://www.asia.apachecon.com/ regards, -jean

[jira] Commented: (DERBY-396) Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN

[ http://issues.apache.org/jira/browse/DERBY-396?page=comments#action_12416580 ] Wade Chandler commented on DERBY-396: - Hmmm. I think what Scott said was he is working on it and no where did I see where he said it works. He mentions something working

Re: Did the MessageBundleTest pass before it was made part of derbyall?

Hm, thanks Andrew. That may very well be, but it was also the case that the master file did not get correctly checked in. I was running in the classes directory. I'll run with the jar files, and see what happens, and correct my logic as needed. Meanwhile, I'll remove MessageBundleTest from

Re: [jira] Commented: (DERBY-1032) Create new scripts which follow common practice at Apache

I didn't follow how this solution is going to be backward-compatible. I'm assuming we'll be keeping the old ones around, perhaps invoking the new ones? David Andrew McIntyre (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1032?page=comments#action_12416463 ] Andrew McIntyre

OutBufferedStream test fails on JDK13 platforms ...

I have been seeing this test fail on JDK13 platforms, both SUN and IBM JVMs since the test was committed. Tomohito, do you have access to JDK13 platform and have interest to fix this failure? If not, I can help. Satheesh [bandaram:satheesh] svn log OutBufferedStream.out

[jira] Commented: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

[ http://issues.apache.org/jira/browse/DERBY-578?page=comments#action_12416588 ] Rick Hillegas commented on DERBY-578: - Hi Manish, I'm confused about what I'm supposed to do with the latest attachment. It looks like it might just be the changes to

Re: [jira] Commented: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator

Since only predicatePushdown failed, I generated a context diff for this one file. I already have a bunch of other uncommitted changes in my view, so I'm not sure how I can generate one patch file without pulling in a lot of other stuff. The following sequence of steps should work. 1. Apply the

[jira] Commented: (DERBY-1394) Working With Derby - Introduction and prerequisites - Improvements

[ http://issues.apache.org/jira/browse/DERBY-1394?page=comments#action_12416589 ] Stan Bradbury commented on DERBY-1394: -- Opps please my mistake int he previous comment under #4: s/10.3/10.2 Of course Working With Derby is slated for release with v

[jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

[ http://issues.apache.org/jira/browse/DERBY-930?page=comments#action_12416591 ] Rick Hillegas commented on DERBY-930: - I think that derby-dev should continue to discuss the issue which Olav has analyzed in DERBY-1399. I will continue this discussion

Re: Did the MessageBundleTest pass before it was made part of derbyall?

Yes, I understand, thanks. David Andrew McIntyre wrote: On 6/16/06, David Van Couvering [EMAIL PROTECTED] wrote: Hm, thanks Andrew. That may very well be, but it was also the case that the master file did not get correctly checked in. I was running in the classes directory. I'll run with

Re: [jira] Commented: (DERBY-930) Add support for autoloading of Derby client drivers

Rick Hillegas (JIRA) wrote: I think that derby-dev should continue to discuss the issue which Olav has analyzed in DERBY-1399. I will continue this discussion shortly. If the behaviour change for DERBY-930 is intentional a special release note is needed for this issue in the section

Driver autoloading and engine booting

This topic was raised in an earlier email thread (http://comments.gmane.org/gmane.comp.apache.db.derby.devel/20899) but it does not appear that we agreed on a solution. I would like to re-open this topic and hopefully we can converge on how we want to handle this issue. Olav has analyzed a

Re: Driver autoloading and engine booting

My vote: - Document it for 10.2 - Log a bug - Work on fixing it by booting on first connection rather than when the driver is loaded. -1 on removing the autoloading feature, unless people have evidence that this is going to cause real problems for our users. David Rick Hillegas wrote:

[jira] Created: (DERBY-1423) set CLASSPATH example in testing/README.htm lists an absolute path for jakarta-oro-2.0.8.jar

set CLASSPATH example in testing/README.htm lists an absolute path for jakarta-oro-2.0.8.jar Key: DERBY-1423 URL: http://issues.apache.org/jira/browse/DERBY-1423 Project: Derby

[jira] Commented: (DERBY-396) Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN

[ http://issues.apache.org/jira/browse/DERBY-396?page=comments#action_12416601 ] Rick Hillegas commented on DERBY-396: - Hi Wade, Scott did not submit a patch for this issue and he has moved on to other pursuits. This issue is currently unassigned.

Re: [jira] Commented: (DERBY-1032) Create new scripts which follow common practice at Apache

On 6/16/06, David Van Couvering [EMAIL PROTECTED] wrote: I didn't follow how this solution is going to be backward-compatible. I'm assuming we'll be keeping the old ones around, perhaps invoking the new ones? I was planning on leaving the old ones where they are, it's mentioned towards the end

Re: Possible CPU loop in testProtocol in cross-release scenario?

Bryan Pendleton [EMAIL PROTECTED] writes: I was trying to verify that the changes in DERBY-920 hadn't introduced any new compatibility problems (they shouldn't, because we were changing an internal class, but I wanted to make sure). So I was trying to follow some old tips about how to run

Re: Copyrights redux

On 6/16/06, Rick Hillegas [EMAIL PROTECTED] wrote: Hi Jean, While I'm on the topic: I asked these questions in the context of 10.2, but it seems that issue (2) may apply to 10.1.3 as well. Do the copyright notices for the 10.1.3 release need to conform to the pattern in (2)? Yes, and I've

[jira] Created: (DERBY-1424) Build derbyclient.jar from a dependency list generated by classlister

Build derbyclient.jar from a dependency list generated by classlister - Key: DERBY-1424 URL: http://issues.apache.org/jira/browse/DERBY-1424 Project: Derby Type: Improvement Components: Build

[jira] Updated: (DERBY-1424) Build derbyclient.jar from a dependency list generated by classlister

[ http://issues.apache.org/jira/browse/DERBY-1424?page=all ] Andrew McIntyre updated DERBY-1424: --- Attachment: derbyclient_classlister.patch Attaching a patch for this issue. I haven't had time to thoroughly test it yet due to trouble with the testing

Re: Possible CPU loop in testProtocol in cross-release scenario?

Knut Anders Hatlen [EMAIL PROTECTED] writes: Bryan Pendleton [EMAIL PROTECTED] writes: I was trying to verify that the changes in DERBY-920 hadn't introduced any new compatibility problems (they shouldn't, because we were changing an internal class, but I wanted to make sure). So I was

Re: Possible CPU loop in testProtocol in cross-release scenario?

Anyway, setting those two fields to false in DDMReader.initialize() made the hang go away, and derbynetclientmats runs cleanly with that change. Wonderful! Thanks for the quick analysis, Knut Anders. It sounds like I should open a JIRA issue for this and we should package up your fix and get

Re: OutBufferedStream test fails on JDK13 platforms ...

Hello Satheesh. I have access to JDK13 and have interest to fix it. I start to survey. Best regards. Satheesh Bandaram wrote: I have been seeing this test fail on JDK13 platforms, both SUN and IBM JVMs since the test was committed. Tomohito, do you have access to JDK13 platform and have

Re: OutBufferedStream test fails on JDK13 platforms ...

Hello. I found that JDK13 installed in my development environment can not work... Error message from java virtual machine was as next. [EMAIL PROTECTED]:~$ java -version /usr/local/jdk1.3.1_18/bin/i386/native_threads/java: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot