[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

2006-02-03 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12365076 ] Philip Wilder commented on DERBY-821: - Thank you for the clarification Knut. I apologize for my misinterpretation. Keep up the good work :-) Client driver: Implicitly

[jira] Commented: (DERBY-821) Client driver: Implicitly close exhausted result sets on the server

2006-01-31 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-821?page=comments#action_12364666 ] Philip Wilder commented on DERBY-821: - I'm sorry I just noticed this now Knut but I should bring it to your attention that you are in fact undoing work that was done in

[jira] Resolved: (DERBY-406) Client DataSource should not require user property to be set

2005-09-17 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Philip Wilder resolved DERBY-406: - Fix Version: 10.2.0.0 10.1.1.0 Resolution: Fixed Assign To: Philip Wilder The July 6, patch addressed the original concerns

[jira] Resolved: (DERBY-410) ClientDataSource should not require serverName/portNumber to be set

2005-09-17 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-410?page=all ] Philip Wilder resolved DERBY-410: - Fix Version: 10.1.2.0 10.1.1.0 Resolution: Fixed Assign To: Philip Wilder The July 6, patch addressed the original concerns

[jira] Created: (DERBY-545) Should ResultSet Close implicitly?

2005-08-30 Thread Philip Wilder (JIRA)
Should ResultSet Close implicitly? -- Key: DERBY-545 URL: http://issues.apache.org/jira/browse/DERBY-545 Project: Derby Type: Improvement Components: JDBC Versions: 10.0.2.0, 10.0.2.1, 10.0.2.2, 10.1.1.0, 10.2.0.0, 10.1.1.1

[jira] Reopened: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-08-30 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder reopened DERBY-213: - ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

[jira] Resolved: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-08-30 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder resolved DERBY-213: - Resolution: Fixed As per Kathey's suggestion, I'm changing this resolution to fixed and creating issue DERBY-545 to assauge any lingering concerns I

[jira] Resolved: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-08-29 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder resolved DERBY-213: - Fix Version: 10.2.0.0 Resolution: Incomplete As of revision 264128 Client ResultSet functionality should match embedded. However, the JDBC

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-08-24 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: Derby213patch_Aug242005.patch I have attempted to address the concerns raised by Kathey's email:

[jira] Created: (DERBY-527) Incorrect insane build on windows platform

2005-08-22 Thread Philip Wilder (JIRA)
Incorrect insane build on windows platform -- Key: DERBY-527 URL: http://issues.apache.org/jira/browse/DERBY-527 Project: Derby Type: Bug Components: Build tools Versions: 10.2.0.0 Environment: --

[jira] Updated: (DERBY-527) Incorrect insane build on windows platform

2005-08-22 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-527?page=all ] Philip Wilder updated DERBY-527: Attachment: BuildXML.patch Moves the ensuresanitystate.sane and ensuresanitystate.insane into the evaluate.sane target so they can evaluate the generate.sane

[jira] Commented: (DERBY-527) Incorrect insane build on windows platform

2005-08-22 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-527?page=comments#action_12319612 ] Philip Wilder commented on DERBY-527: - It should be noted that my ant version is 1.6.2 Incorrect insane build on windows platform

[jira] Closed: (DERBY-527) Incorrect insane build on windows platform

2005-08-22 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-527?page=all ] Philip Wilder closed DERBY-527: --- Assign To: Philip Wilder Incorrect insane build on windows platform -- Key: DERBY-527 URL:

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-08-11 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: Derby213patch_Aug112005.patch An interim patch to bring client in line with embedded. Includes the following changes: - Additional tests in

[jira] Created: (DERBY-480) org.apache.derby.tools.ij documentation bug

2005-07-28 Thread Philip Wilder (JIRA)
org.apache.derby.tools.ij documentation bug --- Key: DERBY-480 URL: http://issues.apache.org/jira/browse/DERBY-480 Project: Derby Type: Bug Components: Tools Versions: 10.2.0.0 Reporter: Philip Wilder

[jira] Resolved: (DERBY-480) org.apache.derby.tools.ij documentation bug

2005-07-28 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-480?page=all ] Philip Wilder resolved DERBY-480: - Fix Version: 10.2.0.0 Resolution: Invalid Satheesh is correct. I overlooked the driver option. org.apache.derby.tools.ij documentation bug

[jira] Created: (DERBY-469) Unnecessary if block in the FromBaseTable.bindTableDescriptor() method

2005-07-25 Thread Philip Wilder (JIRA)
Unnecessary if block in the FromBaseTable.bindTableDescriptor() method -- Key: DERBY-469 URL: http://issues.apache.org/jira/browse/DERBY-469 Project: Derby Type: Bug Components: SQL

[jira] Commented: (DERBY-468) Unreserve COUNT keyword, if possible.

2005-07-22 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-468?page=comments#action_12316556 ] Philip Wilder commented on DERBY-468: - Would removing count from the reserved words list potentially create problems with the count aggregate function? Unreserve COUNT

[jira] Updated: (DERBY-461) Network Client Driver 'password=' behaviour is different from Embedded Driver

2005-07-19 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-461?page=all ] Philip Wilder updated DERBY-461: Attachment: Derby461.patch I poked around the DRDA specs a bit looking for any reference to password lengths without much luck. If there is any inherant

[jira] Resolved: (DERBY-409) ClientDataSource setConnectionAttributes(create=true) fails with An attempt was made to access a database, mydbcreate=true, which was not found.

2005-07-19 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-409?page=all ] Philip Wilder resolved DERBY-409: - Fix Version: 10.1.1.0 10.1.1.1 10.2.0.0 Resolution: Fixed With the latest patch I believe this issue can be

[jira] Updated: (DERBY-461) Network Client Driver 'password=' behaviour is different from Embedded Driver

2005-07-15 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-461?page=all ] Philip Wilder updated DERBY-461: Attachment: Derby461.java Uploaded a standalone reproduction of this issue. Network Client Driver 'password=' behaviour is different from Embedded Driver

[jira] Commented: (DERBY-461) Network Client Driver 'password=' behaviour is different from Embedded Driver

2005-07-15 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-461?page=comments#action_12315924 ] Philip Wilder commented on DERBY-461: - There seem to be two places clientside where password length is checked:

[jira] Updated: (DERBY-409) ClientDataSource setConnectionAttributes(create=true) fails with An attempt was made to access a database, mydbcreate=true, which was not found.

2005-07-12 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-409?page=all ] Philip Wilder updated DERBY-409: Attachment: Derby409.patch This is a potential patch for the issue brought up in DERBY-406 connectionAttributes will now default to null (aka no default) It

[jira] Updated: (DERBY-406) Client DataSource should not require user property to be set

2005-07-06 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Philip Wilder updated DERBY-406: Attachment: Derby406_409_410.patch Removed the changes proposed by Dan Debrunner for an alternate patch. This patch makes the following changes - Sets the

[jira] Commented: (DERBY-406) Client DataSource should not require user property to be set

2005-07-06 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315155 ] Philip Wilder commented on DERBY-406: - I think the issue of intermittent failures of this test is discussed in the DERBY-273 issue. Client DataSource should not require

[jira] Commented: (DERBY-410) ClientDataSource should not require serverName/portNumber to be set

2005-07-06 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-410?page=comments#action_12315171 ] Philip Wilder commented on DERBY-410: - Please see DERBY-406 for an update on the status of this issue. ClientDataSource should not require serverName/portNumber to be

[jira] Commented: (DERBY-406) Client DataSource should not require user property to be set

2005-07-06 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315172 ] Philip Wilder commented on DERBY-406: - Existing data sources do not have any properties that have a default. Perhaps I am misunderstanding your comment. While

[jira] Commented: (DERBY-406) Client DataSource should not require user property to be set

2005-07-04 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315009 ] Philip Wilder commented on DERBY-406: - Sorry for any redundancy on this issue but I would like to make sure that everyone is on the same page as per the status of this

[jira] Created: (DERBY-431) Tests needed for verifying proper functioning of ClientBaseDataSource.setConnectionAttributes() method

2005-07-01 Thread Philip Wilder (JIRA)
Tests needed for verifying proper functioning of ClientBaseDataSource.setConnectionAttributes() method -- Key: DERBY-431 URL: http://issues.apache.org/jira/browse/DERBY-431

[jira] Updated: (DERBY-406) Client DataSource should not require user property to be set

2005-07-01 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Philip Wilder updated DERBY-406: Attachment: Derby406_409_410.patch A Combined patch for DERBY-406, DERBY-409 and DERBY-410 #Warning# When testing this patch there were locale (en_CA vs en_US)

[jira] Assigned: (DERBY-406) Client DataSource should not require user property to be set

2005-06-30 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Philip Wilder reassigned DERBY-406: --- Assign To: Philip Wilder Client DataSource should not require user property to be set

[jira] Commented: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-17 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=comments#action_12313920 ] Philip Wilder commented on DERBY-213: - Proposed Changes: The following are a series of changes I propose to rectify the problem of Derby-213 and bring the client code

[jira] Commented: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-16 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=comments#action_12313824 ] Philip Wilder commented on DERBY-213: - * Update * It would seem that the nature of the problem has changed. Stemming from our discussions surrounding the issue

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-14 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: DERBY-213_6_13_2005.txt DERBY-213 chat transcript for June 13, 2005 Background information: It was the intention of both Kathey and I to release a

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-14 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: ResultSet Outline.pdf Expected ResultSet behavior as per JDBC specifications V1.0 ResultSet.next() after last row of FORWARD_ONLY cursor throws an

[jira] Closed: (DERBY-343) Clean up DRDA classes handling of OPNQRY options

2005-06-09 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-343?page=all ] Philip Wilder closed DERBY-343: --- Clean up DRDA classes handling of OPNQRY options Key: DERBY-343 URL:

[jira] Resolved: (DERBY-343) Clean up DRDA classes handling of OPNQRY options

2005-06-09 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-343?page=all ] Philip Wilder resolved DERBY-343: - Resolution: Fixed The patch committed by kmarsden closes this issue. However a cleanup to remove all warnings from DRDA compilation may occur at a later

[jira] Created: (DERBY-343) Clean up related DRDA classes

2005-06-07 Thread Philip Wilder (JIRA)
Clean up related DRDA classes - Key: DERBY-343 URL: http://issues.apache.org/jira/browse/DERBY-343 Project: Derby Type: Sub-task Components: Network Server Versions: 10.0.2.1, 10.0.2.0 Reporter: Philip Wilder Assigned to:

[jira] Updated: (DERBY-343) Clean up related DRDA classes

2005-06-07 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-343?page=all ] Philip Wilder updated DERBY-343: Attachment: Derby213.diff My first potential patch. The patch in question is designed to addressed the problems mentioned in the description for this issue.

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-07 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: DERBY-213_irc_6_7_2005.txt DERBY-213 chat transcript for June 7, 2005 Summary: * Discovered a typo in change file. * Decided a minor change to the

[jira] Assigned: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-02 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder reassigned DERBY-213: --- Assign To: Philip Wilder (was: Kathey Marsden) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-02 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: Client.java Update to previous client submission. ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network

[jira] Assigned: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-02 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder reassigned DERBY-213: --- Assign To: Kathey Marsden If Jira does not support multiple assignees, Philip Wilder can also be considered an assignee. ResultSet.next() after last

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-06-02 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: IRCTranscript_June2_2005.txt Just to mix things up a bit this morning I'll be doing the Summary for the IRC chat Kathey and I had at

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-05-31 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: Client.java Create.java Server.java Stand alone java tests designed to illustrate the DERBY-213 bug. Create:

[jira] Updated: (DERBY-213) ResultSet.next() after last row of FORWARD_ONLY cursor throws an SQL Exception with Network Server

2005-05-31 Thread Philip Wilder (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-213?page=all ] Philip Wilder updated DERBY-213: Attachment: resultset.java A modification to the resultset test to test for DERBY-213 issue ResultSet.next() after last row of FORWARD_ONLY cursor throws an