[jira] Commented: (DERBY-179) Hibernate bad support

[ http://issues.apache.org/jira/browse/DERBY-179?page=comments#action_12332128 ] Kathey Marsden commented on DERBY-179: -- Is this actually a Bug at this point or r is more of a Task? The reason I ask is that it is currently our "Bug" with the most vot

[jira] Commented: (DERBY-375) Specification of incomplete server properties on command line causes NPE with NetworkServerControl when starting the server.

[ http://issues.apache.org/jira/browse/DERBY-375?page=comments#action_12332124 ] Kathey Marsden commented on DERBY-375: -- Reviewed and committed this patch to the trunk. Looks good. Thanks for fixing DERBY-613 too! My only comment would be that perhaps

[jira] Created: (DERBY-629) Update documentation with correct default values for network server properties

Update documentation with correct default values for network server properties -- Key: DERBY-629 URL: http://issues.apache.org/jira/browse/DERBY-629 Project: Derby Type: Sub-task Versions

[jira] Updated: (DERBY-628) setNull() using Types.VARCHAR for a CLOB parameter fails in embedded mode.

[ http://issues.apache.org/jira/browse/DERBY-628?page=all ] A B updated DERBY-628: -- Attachment: setNull.java Attaching a simple program to reproduce the problem. To run against Derby embedded, use java setNull To run against Derby Client, use java setNull

[jira] Created: (DERBY-628) setNull() using Types.VARCHAR for a CLOB parameter fails in embedded mode.

setNull() using Types.VARCHAR for a CLOB parameter fails in embedded mode. -- Key: DERBY-628 URL: http://issues.apache.org/jira/browse/DERBY-628 Project: Derby Type: Bug Components: JDBC

[jira] Updated: (DERBY-375) Specification of incomplete server properties on command line causes NPE with NetworkServerControl when starting the server.

[ http://issues.apache.org/jira/browse/DERBY-375?page=all ] Deepa Remesh updated DERBY-375: --- Attachment: derby-375.diff derby-375.status derbyall_report.txt Attaching a patch 'derby-375.diff' for this problem. Network server

[jira] Created: (DERBY-627) Documentation needs to be updated with correct return type for COUNT functions

Documentation needs to be updated with correct return type for COUNT functions -- Key: DERBY-627 URL: http://issues.apache.org/jira/browse/DERBY-627 Project: Derby Type: Bug Components: Doc

[jira] Updated: (DERBY-522) ERROR X0Y79 raised when adding comments using "--" before sql queries with Network Client

[ http://issues.apache.org/jira/browse/DERBY-522?page=all ] A B updated DERBY-522: -- Attachment: (was: d522_v2.stat) > ERROR X0Y79 raised when adding comments using "--" before sql queries with > Network Client >

[jira] Updated: (DERBY-522) ERROR X0Y79 raised when adding comments using "--" before sql queries with Network Client

[ http://issues.apache.org/jira/browse/DERBY-522?page=all ] A B updated DERBY-522: -- Attachment: (was: d522_v2.patch) > ERROR X0Y79 raised when adding comments using "--" before sql queries with > Network Client > ---

Re: [jira] Created: (DERBY-626) Booting embedded engine requires read permission to derby.jar be granted for all code in the stack

Oh, that's a bad one, thanks for catching this Dan. Daniel John Debrunner (JIRA) wrote: Booting embedded engine requires read permission to derby.jar be granted for all code in the stack --

Re: Proposal about creating shared component (Re: Questions about what is module to be shared (Re: Discussions on Wik ... ))

Weird Freudian slip. I meant "up to a vote" not "up to avoid." Sorry... David W. Van Couvering wrote: OK, I am proposing that addition of any new packages to a shared component be up to avoid. Addition of new classes or methods to an existing shared package should not require a vote. Does

Re: [Db-derby Wiki] Trivial Update of "FrontPage" by DavidVanCouvering

Apache Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for > change notification. > > The following page has been changed by DavidVanCouvering: > http://wiki.apache.org/db-derby/FrontPage > > -

[jira] Created: (DERBY-626) Booting embedded engine requires read permission to derby.jar be granted for all code in the stack

Booting embedded engine requires read permission to derby.jar be granted for all code in the stack -- Key: DERBY-626 URL: http://issues.apache.org/jira/browse/DERBY-626 Project:

[jira] Closed: (DERBY-589) hang on shutdown on zOS (os/390) with Network Server when starting and shutting down networkserver from the same class

[ http://issues.apache.org/jira/browse/DERBY-589?page=all ] Myrna van Lunteren closed DERBY-589: Resolution: Cannot Reproduce (Visible to derby-developers) > hang on shutdown on zOS (os/390) with Network Server when starting and > shutting do

[jira] Commented: (DERBY-522) ERROR X0Y79 raised when adding comments using "--" before sql queries with Network Client

[ http://issues.apache.org/jira/browse/DERBY-522?page=comments#action_12332095 ] A B commented on DERBY-522: --- Thanks for the review, Kathey. I misunderstood what you meant when you initially talked about not trimming for the 10.1 or earlier clients, hence my la

Re: Proposal about creating shared component (Re: Questions about what is module to be shared (Re: Discussions on Wik ... ))

OK, I am proposing that addition of any new packages to a shared component be up to avoid. Addition of new classes or methods to an existing shared package should not require a vote. Does that sound reasonable? Thanks, David TomohitoNakayama wrote: Hello. Kathey Marsden wrote : I think t

[jira] Commented: (DERBY-522) ERROR X0Y79 raised when adding comments using "--" before sql queries with Network Client

[ http://issues.apache.org/jira/browse/DERBY-522?page=comments#action_12332094 ] Kathey Marsden commented on DERBY-522: -- I reviewed this patch and my only comment is that I think that the ij change should strip comments for JCC or for Derby client

[jira] Commented: (DERBY-589) hang on shutdown on zOS (os/390) with Network Server when starting and shutting down networkserver from the same class

[ http://issues.apache.org/jira/browse/DERBY-589?page=comments#action_12332093 ] Kathey Marsden commented on DERBY-589: -- I am having trouble reproducing this on OS/390. The test seems to pass without problems. > hang on shutdown on zOS (os/390) with N

Re: [jira] Commented: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.

HI, RICK. I ALSO AM NOT WILLING TO SEND YOU TO THE STAKE FOR THIS ONE. IF I WERE TO USE ANT WITHOUT ANY PRVEVIOUS EXPOSURE I WOULD PROBABLY USE CAPS TOO. SO GO AHEAD AND KEEP IT AS IS :) DAVID Rick Hillegas wrote: Hi David, Thanks for vetting my responses. One nub remains: I will be

[jira] Commented: (DERBY-614) Execution failed because of a Distributed Protocol Error

[ http://issues.apache.org/jira/browse/DERBY-614?page=comments#action_12332082 ] Bryan Pendleton commented on DERBY-614: --- Kathey says: "it looks like splitQRYDTA assumes it is going to get a CNTQRY after sending each block of data, but in fact in this

Re: [jira] Commented: (DERBY-498) Result set holdability defined inside stored procedures is ignored by server/client

Deepa Remesh wrote: >I have added procedure tests to xaSimplePositive.sql and attached it >with the mail. This patch is only for review. If it is okay, I can >combine it with my previous patch for derby-498 and attach it to the >JIRA issue. > >I ran xaSimplePositive.sql before and after applying m

Re: [jira] Commented: (DERBY-516) Need to incorporate client backward/forward compatibility testing into testing procedures.

Hi David, Thanks for vetting my responses. One nub remains: I will be happy to change my symbol casing if you feel passionately about this. I think, however, that our existing ant scripts are fairly poor examples of ant usage. For instance, they do not take advantage of the -projecthelp machi

[jira] Updated: (DERBY-614) Execution failed because of a Distributed Protocol Error

[ http://issues.apache.org/jira/browse/DERBY-614?page=all ] Bryan Pendleton updated DERBY-614: -- Attachment: serverSideTrace.txt Server side tracing of the error. Corresponds with the attachment clientSideTrace.txt. > Execution failed because of a Dist

[jira] Updated: (DERBY-614) Execution failed because of a Distributed Protocol Error

[ http://issues.apache.org/jira/browse/DERBY-614?page=all ] Bryan Pendleton updated DERBY-614: -- Attachment: clientSideTrace.txt Client side of a pair of matching trace files surrounding the error. Corresponds to the attachment serverSideTrace.txt. > E

[jira] Commented: (DERBY-614) Execution failed because of a Distributed Protocol Error

[ http://issues.apache.org/jira/browse/DERBY-614?page=comments#action_12332076 ] Bryan Pendleton commented on DERBY-614: --- It occurred to me that it would probably be most useful to have a matching set of client-side and server-side tracing. So I've re

[jira] Resolved: (DERBY-624) Running derbynetclientmats and derbynetmats requires accessDeclaredMembers permission to be granted with sane=true

[ http://issues.apache.org/jira/browse/DERBY-624?page=all ] Daniel John Debrunner resolved DERBY-624: - Fix Version: 10.2.0.0 Resolution: Fixed > Running derbynetclientmats and derbynetmats requires accessDeclaredMembers > permission to

Re: [jira] Commented: (DERBY-498) Result set holdability defined inside stored procedures is ignored by server/client

Sorry I missed to attach the patch with my previous mail. Just want to add that I had run the new xaSimplePositive.sql with embedded and client driver. In both cases, I did not get error when the holdability of a statement inside a procedure was set to HOLD_CURSORS_OVER_COMMIT in a xa transaction.

[jira] Commented: (DERBY-614) Execution failed because of a Distributed Protocol Error

[ http://issues.apache.org/jira/browse/DERBY-614?page=comments#action_12332071 ] Kathey Marsden commented on DERBY-614: -- The server side tracing information is on the Wiki page as weel. Looking briefly at your trace and at the splitQRYDTA code it looks