[jira] Updated: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=all ] V.Narayanan updated DERBY-1445: --- Attachment: ver3-washed-v1.diff ver3-washed-v1.stat Hi, thanx a ton for the commit. Please find attached the follow-up patch with the comments

[jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ] Kristian Waagan updated DERBY-1417: --- Attachment: derby-1417-1a-notImplemented.diff derby-1417-1a-notImplemented.stat 'derby-1417-1a-notImplemented.diff' adds a number of new

[jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ] Kristian Waagan updated DERBY-1417: --- Derby Info: [Patch Available] Add new, lengthless overloads to the streaming api -- Key:

[jira] Resolved: (DERBY-1445) Add new streaming overloads and modify some existing ones.

[ http://issues.apache.org/jira/browse/DERBY-1445?page=all ] Knut Anders Hatlen resolved DERBY-1445: --- Fix Version: 10.2.0.0 Resolution: Fixed Thanks! Committed the follow-up patch into trunk with revision 417705. Add new streaming

[jira] Updated: (DERBY-1043) Invalid column references are not caught in a trigger action statement when the referencing table of the column is the triggered table

[ http://issues.apache.org/jira/browse/DERBY-1043?page=all ] Fernanda Pizzorno updated DERBY-1043: - Attachment: derby-1043.diff derby-1043.stat I tried a similar update statement as the one in the trigger to see if the problem was

[jira] Updated: (DERBY-1043) Invalid column references are not caught in a trigger action statement when the referencing table of the column is the triggered table

[ http://issues.apache.org/jira/browse/DERBY-1043?page=all ] Fernanda Pizzorno updated DERBY-1043: - Derby Info: [Patch Available] Invalid column references are not caught in a trigger action statement when the referencing table of the column is

Re: Proposal for 10.2 release schedule

Hi Mike, Some responses follow. Regards-Rick Mike Matrigali wrote: Rick Hillegas wrote: Thanks, Kathy. I think I'm getting the message that the following would be an acceptable and more traditional schedule: August 10 : Last feature work commits August 11 : First release candidate

[jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ] Knut Anders Hatlen updated DERBY-1417: -- Derby Info: (was: [Patch Available]) Committed 'derby-1417-1a-notImplemented.diff' into trunk with revision 417753. Add new, lengthless

Re: [jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

Kristian Waagan (JIRA) wrote: I will add tests, but have to wait until the signatures have made it into Mustang (I do have some tests already, but here I use the specific implementation classes, not the interfaces). It seems to me that it's completely appropriate for tests to use specific

[jira] Created: (DERBY-1461) Separate writeScalarStream to methods which handle either encrypted or plain streams.

Separate writeScalarStream to methods which handle either encrypted or plain streams. - Key: DERBY-1461 URL: http://issues.apache.org/jira/browse/DERBY-1461 Project: Derby Type:

[jira] Assigned: (DERBY-1461) Separate writeScalarStream to methods which handle either encrypted or plain streams.

[ http://issues.apache.org/jira/browse/DERBY-1461?page=all ] Tomohito Nakayama reassigned DERBY-1461: Assign To: Tomohito Nakayama Separate writeScalarStream to methods which handle either encrypted or plain streams.

[jira] Commented: (DERBY-822) Client driver: Pre-fetch data on executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12418258 ] Knut Anders Hatlen commented on DERBY-822: -- Kathey Marsden wrote: 1) Queries may fail earlier. Instead of failing on the ResultSet next() call, they may now

Re: [VOTE] 10.1.3.1 release

1. PGP signature verified. 2. MD5 sum verified 3. Derbyall run (in Dublin, at ApacheCon on my little laptop with Ubuntu 5.10) with 1 fail: derbyall/derbyall.fail:unit/T_Diagnosticable.unit Seems to me to be DERBY-496 (Top of derby.log attached) Platform: Java Version:1.4.2_09 OS name:

Re: [jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

Bryan Pendleton wrote: Kristian Waagan (JIRA) wrote: I will add tests, but have to wait until the signatures have made it into Mustang (I do have some tests already, but here I use the specific implementation classes, not the interfaces). It seems to me that it's completely appropriate

Re: [jira] Updated: (DERBY-1417) Add new, lengthless overloads to the streaming api

You are correct that using specific implementation classes is completely appropriate in general. However, in this case, I would not be able to *easily* share the test code between the embedded and the client driver when running the JUnit test in our harness (I'm not very fond of the master

Regression Test Failure! - TinderBox_Derby 417756 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 417756/2006-06-28 15:53:05 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2675673 2 160.28% SunOS-5.10_i86pc-i386 Details in

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v02.diff Attaching bug1459_v02.diff, which hopefully addresses Dan's concern. In this version the public EmbeddedDriver has a rather

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

[ http://issues.apache.org/jira/browse/DERBY-578?page=all ] Kathey Marsden updated DERBY-578: - Attachment: derby578_06282006_diff.txt In the interest of learning a little about a different code area I did a bit of housekeeping on this patch.

ApacheCon US 2006 CFP -- Last Call for Proposals!

Today is the deadline for ApacheCon US proposals. -jean Original Message Subject: ApacheCon US 2006 CFP Date: Tue, 20 Jun 2006 12:15:37 -0700 From: Jean T. Anderson [EMAIL PROTECTED] Reply-To: derby-dev@db.apache.org, [EMAIL PROTECTED] To: Derby Development

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12418285 ] Kathey Marsden commented on DERBY-1459: --- The functional description as you have outlined it sounds great and I think would solve all the scenarios outlined. I haven't

lang/predicatePushdown.sql diff in tinderbox

[EMAIL PROTECTED] wrote: [Auto-generated mail] *TinderBox_Derby* 417756/2006-06-28 15:53:05 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2675673 2 160.28% SunOS-5.10_i86pc-i386 I

Issue with using dependency manager for table level permission tracking

Hi, I recently submitted a patch (http://www.nabble.com/-PATCH-DERBY-1330-Collect-privilege-requirements-for-views-tf1858264.html#a5075008 )that tracks a view's(view descriptor)dependency on different privileges (PermissionsDescriptor)using the dependency manager which in turn saves these

Re: [jira] Commented: (DERBY-1275) Provide a way to enable client tracing without changing the application

This sounds like a perfect case for JMX soultion and can be added to list of requirements on derby Wiki. Tracing options (enable/disable) and perhaps the file name can be exposed as JMX operations. While debugging the application the developers can start derby in JMX mode and enable/disable

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12418294 ] Rick Hillegas commented on DERBY-1459: -- Hi Kathey, With the new patch, the public interfaces should not change. Thanks for recommending those tests. I will add them to

[jira] Commented: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is

[ http://issues.apache.org/jira/browse/DERBY-1459?page=comments#action_12418299 ] Daniel John Debrunner commented on DERBY-1459: -- The functional behaviour of EmbeddedDriver changes with this patch. Previously calls to the java.sql.Driver

Re: [VOTE] 10.1.3.1 release

Andrew McIntyre wrote: Hello derby-dev, I have posted a new release candidate for 10.1.3 here: http://people.apache.org/~fuzzylogic/10.1.3.1/ +1 I tried the frameworks\NetworkServer batch files on Windows XP and the nserverdemo/SimpleNetworkClientSample.java demo which worked ok. My

Preview: High Level Design for JMX

Hi, While was drafting the High Level Design document for JMX extensions I thought of putting it up on the wiki for some early feedback. The HLD can be accessed here : http://wiki.apache.org/db-derby/High_Level_Design Please note that: 1) This is draft document and is subject to constant

Re: Preview: High Level Design for JMX

Hi, Sanket, thanks for this initial draft. Here are some comments. Section 5.2 - I think you might to say Derby JMX Components because the last section was a general overview of JMX, and one might think this was still about JMX in general - In the figure you have a JDBC Service MBean, but

Re: Preview: High Level Design for JMX

- I think you might to say Derby JMX Components because the last section was a general overview of JMX, and one might think this was still about JMX in general okay. - In the figure you have a JDBC Service MBean, but in the table it's not there and you have a Driver MBean. Are these the

Re: Preview: High Level Design for JMX

Sanket Sharma wrote: - I think it might be worth going int more detail on how a Model MBean works since this is what you're proposing to use. I liked this text from http://www.admc.com/blaine/howtos/jmx/ch06.html Umm...I have mixed feelings on that. I initially thought a sperate article

[jira] Updated: (DERBY-1459) Early load of Derby driver with JDBC 4.0 autoloading can lead to derby properties not being processed or derby boot time actions consuming resources when a connection is m

[ http://issues.apache.org/jira/browse/DERBY-1459?page=all ] Rick Hillegas updated DERBY-1459: - Attachment: bug1459_v03.diff Thanks for continuing to review these patches, Dan. I've attached another rev, bug1459_v03.diff. I hope this is converging on a

How do you pronounce Derby?

I've been getting this question lately, so I started a Wiki page: http://wiki.apache.org/db-derby/DerbyPronunciation Feel free to add your pronunciation to it. -jean

Re: [VOTE] 10.1.3.1 release

+1 I verified my fixes and I believe this release has a good set of fixes for a release. We should go with this release candidate. Thanks to everyone who worked hard getting fixes in. Andrew McIntyre wrote: Hello derby-dev, I have posted a new release candidate for 10.1.3 here:

[jira] Commented: (DERBY-526) Network Client URL cannot take the IP Address as host name for IPV6 machines

[ http://issues.apache.org/jira/browse/DERBY-526?page=comments#action_12418338 ] Manjula Kutty commented on DERBY-526: - Please add this to the Release Notes: PROBLEM NumberFormatException while trying to get connection to a Ipv6 server using the ip

[jira] Updated: (DERBY-1428) Generating derby properties on the fly can lead to non-deterministic engine startup behavior

[ http://issues.apache.org/jira/browse/DERBY-1428?page=all ] Mike Matrigali updated DERBY-1428: -- Component: Services (was: Store) changing component from store to services. This is really a monitor issue. Generating derby

[jira] Commented: (DERBY-283) On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .

[ http://issues.apache.org/jira/browse/DERBY-283?page=comments#action_12418340 ] Manjula Kutty commented on DERBY-283: - Please add thi to the Release Notes: PROBLEM UnknownHost Exception while trying to connect with NetworkClient on a Windows dual

[jira] Created: (DERBY-1462) Test harness incorrectly catches db.lck WARNINGS generated during STORE tests and lists the tests as failed in *_fail.txt.

Test harness incorrectly catches db.lck WARNINGS generated during STORE tests and lists the tests as failed in *_fail.txt. -- Key: DERBY-1462 URL:

[jira] Updated: (DERBY-283) On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while starting the server .

[ http://issues.apache.org/jira/browse/DERBY-283?page=all ] Manjula Kutty updated DERBY-283: Derby Info: [Release Note Needed] On IPv6/Ipv4 dual stack windows machines, the network server needs the following jvm properties to be prefixed while

JIRA question - what to do with issues that are verified JVM issues rather than derby bugs?

I have verfied that DERBY=1280 is a JVM bug specific to the reported IBM JVM bug. What should I do with the jira issue? Also any opinions on if the error message should be changed. Basically all that the code knows is that it got an IO exception while trying to write a page out, it does nest

[jira] Updated: (DERBY-526) Network Client URL cannot take the IP Address as host name for IPV6 machines

[ http://issues.apache.org/jira/browse/DERBY-526?page=all ] Manjula Kutty updated DERBY-526: Derby Info: [Release Note Needed] Network Client URL cannot take the IP Address as host name for IPV6 machines

[jira] Resolved: (DERBY-407) predicatesIntoViews test failure on slow machine in Derby 10.1 branch version 201931

[ http://issues.apache.org/jira/browse/DERBY-407?page=all ] A B resolved DERBY-407: --- Resolution: Fixed The derby.optimizer.noTimeout workaround (as commited almost a year ago) allows this test to run without failure and seems like the appropriate fix

[jira] Closed: (DERBY-407) predicatesIntoViews test failure on slow machine in Derby 10.1 branch version 201931

[ http://issues.apache.org/jira/browse/DERBY-407?page=all ] A B closed DERBY-407: - predicatesIntoViews test failure on slow machine in Derby 10.1 branch version 201931

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

[ http://issues.apache.org/jira/browse/DERBY-1015?page=comments#action_12418344 ] Sunitha Kambhampati commented on DERBY-1015: Thanks for the feedbac, Dan. Looking at this some more, I think it is better to define a new interface for

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

[ http://issues.apache.org/jira/browse/DERBY-959?page=all ] Sunitha Kambhampati reassigned DERBY-959: - Assign To: Sunitha Kambhampati Allow use of DRDA QRYDTA block sizes greater than 32K -

minor javadoc warnings in trunk

Noticed following javadoc warnings in trunk: [javadoc] opensource\java\engine\org\apache\derby\iapi\jdbc\BrokeredCallableStatement40.java:287: warning - @param argument parameterIndex is not a parameter name. [javadoc]

[jira] Created: (DERBY-1463) Resolve javadoc warnings in BrokeredCallableStatement40

Resolve javadoc warnings in BrokeredCallableStatement40 --- Key: DERBY-1463 URL: http://issues.apache.org/jira/browse/DERBY-1463 Project: Derby Type: Bug Components: Javadoc Reporter: V.Narayanan

[jira] Assigned: (DERBY-1463) Resolve javadoc warnings in BrokeredCallableStatement40

[ http://issues.apache.org/jira/browse/DERBY-1463?page=all ] V.Narayanan reassigned DERBY-1463: -- Assign To: V.Narayanan Resolve javadoc warnings in BrokeredCallableStatement40 --- Key: