Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

Bryan Pendleton wrote: Kristian Waagan commented on DERBY-1471: The approach is to exhaust the application stream and copy it into memory to determine the length. If the data is too big to fit in memory, the client will fail with an

[jira] Updated: (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 ] Andreas Korneliussen updated DERBY-1064: Fix Version: 10.2.0.0 Version: 10.2.0.0 Committed revision 419186 at trunk. Delete cascade causes NULL values inserted into table

[jira] Created: (DERBY-1476) PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types

PreparedStatement.setNull(int,int) should throw SQLFeatureNotSupportedException for unsupported types - Key: DERBY-1476 URL: http://issues.apache.org/jira/browse/DERBY-1476

[jira] Created: (DERBY-1477) create JUnit tests for testing LOB OutOfMemory problems

create JUnit tests for testing LOB OutOfMemory problems --- Key: DERBY-1477 URL: http://issues.apache.org/jira/browse/DERBY-1477 Project: Derby Type: Sub-task Components: Test Versions: 10.2.0.0

[jira] Updated: (DERBY-1475) lang/procedure.java intermittently fails on SunOS-5.10_i86

[ http://issues.apache.org/jira/browse/DERBY-1475?page=all ] Fernanda Pizzorno updated DERBY-1475: - Attachment: derby-1475.diff derby-1475.stat I had not seen the new diff in DERBY-1320 after the applying the same fix as for

[jira] Updated: (DERBY-1475) lang/procedure.java intermittently fails on SunOS-5.10_i86

[ http://issues.apache.org/jira/browse/DERBY-1475?page=all ] Fernanda Pizzorno updated DERBY-1475: - Derby Info: [Patch Available] lang/procedure.java intermittently fails on SunOS-5.10_i86 --

Regression Test Failure! - Derby 419055 - Sun DBTG

[Auto-generated mail] *Derby* 419055/2006-07-04 19:46:18 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* NA NA NANA SunOS-5.10_i86pc-i386 Details in

[jira] Updated: (DERBY-1477) create JUnit tests for testing BLOB OutOfMemory problems

[ http://issues.apache.org/jira/browse/DERBY-1477?page=all ] Andreas Korneliussen updated DERBY-1477: Summary: create JUnit tests for testing BLOB OutOfMemory problems (was: create JUnit tests for testing LOB OutOfMemory problems)

Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

John Embretsen wrote: Bryan Pendleton wrote: Kristian Waagan commented on DERBY-1471: The approach is to exhaust the application stream and copy it into memory to determine the length. If the data is too big to fit in memory, the client

[jira] Commented: (DERBY-694) Statement exceptions cause all the connection's result sets to be closed with the client driver

[ http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12419265 ] V.Narayanan commented on DERBY-694: --- When a exception(in the attached file divide by zero) occurs upon statement execution it results in calling a

[jira] Updated: (DERBY-1477) create JUnit tests for testing BLOB OutOfMemory problems

[ http://issues.apache.org/jira/browse/DERBY-1477?page=all ] Andreas Korneliussen updated DERBY-1477: Attachment: DERBY-1477.diff DERBY-1477.stat Attaching test patch. The test has 4 testcases. The 2 testcases which uses

[jira] Updated: (DERBY-1477) create JUnit tests for testing BLOB OutOfMemory problems

[ http://issues.apache.org/jira/browse/DERBY-1477?page=all ] Andreas Korneliussen updated DERBY-1477: Derby Info: [Patch Available] create JUnit tests for testing BLOB OutOfMemory problems

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

[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-testfix.diff derby-989-testfix.stat derby-989-testfix.diff is an alternative solution. This patch only changes

Where does the Client Driver expand object into memory before sending it ? (Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0)

Hello. Concerning about use of memory at driver, I briefly surveyed client driver program to find where *whole of* object was expanded into memory before sending it, from code searched with keyword writeScalarStream as starting point of survey. The result was as next. When

Re: Where does the Client Driver expand object into memory before sending it ? (Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0)

Hello. I think this should be told in DERBY-1472 more than DERBY-1471 .. Best regards. TomohitoNakayama wrote: Hello. Concerning about use of memory at driver, I briefly surveyed client driver program to find where *whole of* object was expanded into memory before sending it, from code

[jira] Commented: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

[ http://issues.apache.org/jira/browse/DERBY-1248?page=comments#action_12419280 ] Knut Anders Hatlen commented on DERBY-1248: --- I also see this failure on Linux, but not as frequently as on Solaris (had to run the test 125 times on Linux, whereas

Re: [jira] Commented: (DERBY-1237) unit/daemonService fails intermittently with Shutting down due to unit test failure.

Bryan Pendleton wrote: Knut Anders Hatlen commented on DERBY-1237: --- Does anyone object to closing this issue as a duplicate of 989? Thanks for having a close read of the logs. Closing as a duplicate seems reasonable to me. bryan I agree, I

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

Knut Anders Hatlen (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen updated DERBY-989: - Attachment: derby-989-testfix.diff derby-989-testfix.stat derby-989-testfix.diff is an

Re: [jira] Commented: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

Knut Anders Hatlen (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1248?page=comments#action_12419280 ] Knut Anders Hatlen commented on DERBY-1248: --- I also see this failure on Linux, but not as frequently as on Solaris (had to run

Re: [jira] Commented: (DERBY-1248) Assert failure in BasePage.shiftUp() when running store/onlineBackupTest4.sql

Knut Anders Hatlen (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1248?page=comments#action_12419280 ] Knut Anders Hatlen commented on DERBY-1248: --- I also see this failure on Linux, but not as frequently as on Solaris (had to run

[jira] Updated: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=all ] Kathey Marsden updated DERBY-1446: -- Attachment: ReproScenario.zip Larry Dunnell who works with WTP made a new repro which removes WTP from the issue. We still need source for the stored

Re: [jira] Commented: (DERBY-883) Enhance GROUP BY clause to support expressions instead of just column references.

Hi Manish, Do you have any updates on your progress to share with us? It seemed you had a good design to support GROUP BY expressions last time it was discussed. Would this be ready in time for 10.2? I have itch to see this issue progress and can help. Even if you have basic framework for

[jira] Commented: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=comments#action_12419314 ] Kathey Marsden commented on DERBY-1446: --- To clarify the repro without WTP is ReproScenario.zip Derby can enter infinite loop and consume 100% cpu when loading class

Re: 10.1.3.1 release notes draft page

Andrew McIntyre wrote: I've posted a new draft of the release notes page at: http://people.apache.org/~fuzzylogic/releases/release-10.1.3.1.html Please let me know if you find any issues with this draft. Thanks, andrew Hi Andrew, I had run the system/stress test on redhat linux with

Re: 10.1.3.1 release notes draft page

On 7/5/06, Manjula G Kutty [EMAIL PROTECTED] wrote: Andrew McIntyre wrote: I've posted a new draft of the release notes page at: http://people.apache.org/~fuzzylogic/releases/release-10.1.3.1.html Please let me know if you find any issues with this draft. Thanks, andrew Hi Andrew, I

Re: Re: 10.1.3.1 release notes draft page

On 7/5/06, Myrna van Lunteren [EMAIL PROTECTED] wrote: Hi Andrew, I had run the system/stress test on redhat linux with ibm142 and ibm15(without jit). Please update this info for the '?' marks Thanks Manjula And I had run the CTS tests with sun jdk 1.4.2_07-b05 on Windows 2000. Please

Re: Re: Re: 10.1.3.1 release notes draft page

On 7/5/06, Andrew McIntyre [EMAIL PROTECTED] wrote: Last call for changes to the release notes! If I don't hear anything in the next hour or so, I will commit the changes to the website and announce the release. A new draft with Myrna and Manjula's additional information is now visible at:

How to add a new service to Derby?

Hi, I was tinkering with Derby code for some time with JMX in my mind. I was wondering if there is a recommended way of adding new services to derby? The code documentation in Monitor.java says describes following ways to boot services (please correct me if I'm wrong): 1) having a property in

Re: [jira] Commented: (DERBY-883) Enhance GROUP BY clause to support expressions instead of just column references.

Actually, I'm still working on it and have got it working for the most part. I still need to cleanup the code, add more error messages, more compile time checks and tests (all the fun stuff) before its ready for checkin. What is the timeframe for getting things into 10.2? m --- Satheesh

Re: [jira] Commented: (DERBY-1368) EOFException when reading from blob's binary stream

Kathey Marsden (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1368?page=comments#action_12418747 ] So it does seem to be fixed but don't know exactly what fixed it. I think this particular issue has been fixed as a result of the changes that Dan made as part of Derby-438,

[jira] Resolved: (DERBY-959) Allow use of DRDA QRYDTA block sizes greater than 32K

[ http://issues.apache.org/jira/browse/DERBY-959?page=all ] Sunitha Kambhampati resolved DERBY-959: --- Resolution: Fixed This fix has been code for sometime. I have verified this fix with the odbc client driver. Allow use of DRDA QRYDTA

[jira] Commented: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[ http://issues.apache.org/jira/browse/DERBY-1272?page=comments#action_12419342 ] Kathey Marsden commented on DERBY-1272: --- Is it ok to go ahead and mark this issue as patch available? It would be good to get input from those familiar with the

[jira] Closed: (DERBY-959) Allow use of DRDA QRYDTA block sizes greater than 32K

[ http://issues.apache.org/jira/browse/DERBY-959?page=all ] Bryan Pendleton closed DERBY-959: - Thanks Sunitha for addressing this! Fix verified as complete. Allow use of DRDA QRYDTA block sizes greater than 32K

[jira] Commented: (DERBY-1446) Derby can enter infinite loop and consume 100% cpu when loading class when running a stored procedure within Eclipse 3.2

[ http://issues.apache.org/jira/browse/DERBY-1446?page=comments#action_12419355 ] Kathey Marsden commented on DERBY-1446: --- Eclipse Equinox/Framework Bug 149754 has been created. https://bugs.eclipse.org/bugs/show_bug.cgi?id=149754 There appears to

[jira] Closed: (DERBY-1426) Derby Server and Administration Guide - Using the Derby ij tool with the Network Server

[ http://issues.apache.org/jira/browse/DERBY-1426?page=all ] Halley Pacheco de Oliveira closed DERBY-1426: - Derby Server and Administration Guide - Using the Derby ij tool with the Network Server

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

[ http://issues.apache.org/jira/browse/DERBY-989?page=comments#action_12419356 ] Suresh Thalamati commented on DERBY-989: Hi Knut, Thanks for looking into this failure. I took a quick look at your changes,patch looks good. Only minor thing I

[jira] Commented: (DERBY-1345) net/Reply.writeScalarStream() simply prints stack trace on encryption exception

[ http://issues.apache.org/jira/browse/DERBY-1345?page=comments#action_12419361 ] Sunitha Kambhampati commented on DERBY-1345: I took a very quick look at this and wanted to post what I found. -- The code snippet in the jira description is

[ANNOUNCE] Apache Derby 10.1.3.1 released

The Apache Derby project is pleased to announce the release of Derby 10.1.3.1, a maintenance release of Derby 10.1. Apache Derby is a subproject of the Apache DB project. Derby is a pure Java, standards-based relational database engine. Derby aims to be an easy to use solution for data

[jira] Updated: (DERBY-1345) net/Request.writeScalarStream() simply prints stack trace on encryption exception

[ http://issues.apache.org/jira/browse/DERBY-1345?page=all ] Sunitha Kambhampati updated DERBY-1345: --- Summary: net/Request.writeScalarStream() simply prints stack trace on encryption exception (was: net/Reply.writeScalarStream() simply prints

[jira] Updated: (DERBY-1053) stress.multi test on ibm142 in SANE builds fails with ASSERTION at org.apache.derby.impl.services.cache.CachedItem.unkeep(CachedItem.java:152)

[ http://issues.apache.org/jira/browse/DERBY-1053?page=all ] Mike Matrigali updated DERBY-1053: -- Component: Regression Test Failure stress.multi test on ibm142 in SANE builds fails with ASSERTION at

[jira] Assigned: (DERBY-1208) Attempts to reuse a prepared statement after an execution-time error causes ASSERT failure in SANE mode, but work fine in INSANE.

[ http://issues.apache.org/jira/browse/DERBY-1208?page=all ] Andrew McIntyre reassigned DERBY-1208: -- Assign To: Håvard Mork Attempts to reuse a prepared statement after an execution-time error causes ASSERT failure in SANE mode, but work fine in

[jira] Updated: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[ http://issues.apache.org/jira/browse/DERBY-1272?page=all ] Andrew McIntyre updated DERBY-1272: --- Derby Info: [Patch Available] Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[jira] Updated: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[ http://issues.apache.org/jira/browse/DERBY-1272?page=all ] Andrew McIntyre updated DERBY-1272: --- Attachment: derby-1272-pre3.diff Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[jira] Commented: (DERBY-1272) Change sysinfo to print to error log (derby.log) on boot of derby if derby.stream.error.logSeverityLevel=0

[ http://issues.apache.org/jira/browse/DERBY-1272?page=comments#action_12419372 ] Andrew McIntyre commented on DERBY-1272: Attached patch -pre3. Disregard -pre2 patch, which got mixed up with the patch currently attached to 1273. Change sysinfo

DERBY-1072 (Misleading/wrong error message while dropping a view)- is this fixed now?

Is DERBY-1072 done? From comments in the jira it looks like the last patch was committed.

[jira] Updated: (DERBY-1015) Define interface between network server and engine through Java interfaces.

[ http://issues.apache.org/jira/browse/DERBY-1015?page=all ] Sunitha Kambhampati updated DERBY-1015: --- Attachment: derby1015.diff.txt derby1015.stat.txt I have been looking at derby1015 in context of fixing derby-1227. I am

Re: DERBY-1072 (Misleading/wrong error message while dropping a view)- is this fixed now?

On 7/5/06, Mike Matrigali [EMAIL PROTECTED] wrote: Is DERBY-1072 done? From comments in the jira it looks like the last patch was committed. Yes, I believe so. I've marked it resolved. andrew

[jira] Resolved: (DERBY-1072) Misleading/wrong error message while dropping a view

[ http://issues.apache.org/jira/browse/DERBY-1072?page=all ] Andrew McIntyre resolved DERBY-1072: Fix Version: 10.2.0.0 Resolution: Fixed Marking resolved, as no further test diffs were noted. Manjula, please close this if you are

DERBY-396: Drop Column dependency questions

I've been writing additional tests for ALTER TABLE DROP COLUMN and have come across a few questions: 1) When I specify RESTRICT, the code searches for dependent objects and rejects the DROP COLUMN if a dependent item is found. However, an index is apparently not considered a dependent item. That