[jira] Resolved: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

[ http://issues.apache.org/jira/browse/DERBY-416?page=all ] Andrew McIntyre resolved DERBY-416: --- Fix Version: 10.1.1.0 10.2.0.0 Resolution: Fixed Committed, revision 202492 to trunk. Will merge to 10.1 branch before release.

Re: [jira] Commented: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

On Jun 29, 2005, at 11:20 PM, Mamta Satoor wrote: I have attached a patch to Derby-416 Parameter in one of the error messages is not replaced by the desired value If the patch looks good, can a commiter please commit this? thanks, Mamta This looks like a very straightforward fix. I'll tak

Re: [jira] Commented: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

I have attached a patch to Derby-416 Parameter in one of the error messages is not replaced by the desired value   If the patch looks good, can a commiter please commit this?   thanks, Mamta  On 6/29/05, Mamta A. Satoor (JIRA) wrote:    [ http://issues.apache.org/jira/brow

[jira] Commented: (DERBY-405) SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables

[ http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314739 ] Mamta A. Satoor commented on DERBY-405: --- Forgot to mention earlier, but if we decide to fix this issue then it will have documentation impact and we would need to mention

[jira] Updated: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

[ http://issues.apache.org/jira/browse/DERBY-416?page=all ] Mamta A. Satoor updated DERBY-416: -- Attachment: Derby416FixErrorText062905.txt > Parameter in one of the error messages is not replaced by the desired value. > -

Re: Are SYNONYMS exposed through DatabaseMetaData.getTables() api?

Hi Satheesh,   Just wondered if you got a chance to look at following. Also, if this is supported then is there a test for it?   thanks, Mamta  On 6/15/05, Mamta Satoor <[EMAIL PROTECTED]> wrote: Hi Satheesh,   I was wondering if a JDBC program can use DatabaseMetaData.getTables() to get the synon

[jira] Commented: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

[ http://issues.apache.org/jira/browse/DERBY-416?page=comments#action_12314738 ] Mamta A. Satoor commented on DERBY-416: --- The problem was with using ' in the error text message ie the text for XJ084 in messages_en.properties currently looks like follo

[jira] Updated: (DERBY-408) Fix formatting of manuals in PDF output

[ http://issues.apache.org/jira/browse/DERBY-408?page=all ] Jeff Levitt updated DERBY-408: -- Summary: Fix formatting of manuals in PDF output (was: Fix formatting of syntax sections in manuals) Description: 1. The syntax boxes in many of the Derby

Re: [PATCH]updatableResultSet.out master file for jdk13 and Network Server combination using Derby Net Client

Thanks, Andrew. On 6/29/05, Andrew McIntyre <[EMAIL PROTECTED]> wrote: On Jun 27, 2005, at 11:36 PM, Mamta Satoor wrote: Hi,   While running updatableResultSet.java using jdk13 under Network Server(using Derby Net Client), I realized that we need a special master for jdk13. Currently, there is o

Re: [PATCH]updatableResultSet.out master file for jdk13 and Network Server combination using Derby Net Client

On Jun 27, 2005, at 11:36 PM, Mamta Satoor wrote:Hi,   While running updatableResultSet.java using jdk13 under Network Server(using Derby Net Client), I realized that we need a special master for jdk13. Currently, there is only one master for Network Server (using Derby Net Client) at java\testing\

Re: [PATCH]updatableResultSet.out master file for jdk13 and Network Server combination using Derby Net Client

Will someone this commit for me?   thanks, Mamta  On 6/27/05, Mamta Satoor <[EMAIL PROTECTED]> wrote: Hi,   While running updatableResultSet.java using jdk13 under Network Server(using Derby Net Client), I realized that we need a special master for jdk13. Currently, there is only one master for N

[STATUS] (Derby) Wed Jun 29 23:45:28 2005

APACHE DERBY STATUS: Last modified at [$Date: 2005-06-16 00:08:03 -0400 (Thu, 16 Jun 2005) $] by $Author: jboynes $. Web site: http://incubator.apache.org/derby/ Incubator Status Description "Derby" is a snapshot of the IBM's Cloudscape Java relational database. IBM is opening the code b

[jira] Assigned: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

[ http://issues.apache.org/jira/browse/DERBY-416?page=all ] Mamta A. Satoor reassigned DERBY-416: - Assign To: Mamta A. Satoor > Parameter in one of the error messages is not replaced by the desired value. > ---

[jira] Updated: (DERBY-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby

[ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: -- Attachment: derby379modified.diff Attached patch fixes the page requested by Myrna and returns the \lib directory to the paths where they were removed in the first

[jira] Commented: (DERBY-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual

[ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314722 ] Jeff Levitt commented on DERBY-382: --- >From Derby-166 (which is resolved as a duplicate of this issue now): The following statement in the documentation is incorrect: NULL T

[jira] Resolved: (DERBY-166) NULL is not a valid constraint type

[ http://issues.apache.org/jira/browse/DERBY-166?page=all ] Jeff Levitt resolved DERBY-166: --- Resolution: Duplicate I am adding this comment to the doc review for the reference manual for version 10.1. It will get patched there... Thus, resolving th

[jira] Commented: (DERBY-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual

[ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314720 ] Jeff Levitt commented on DERBY-382: --- Adding Kathey Marsden's comment on Derby-275 that was added after that issue was committed: REGARDING THIS PARAGRAPH: Note that unlike

[jira] Assigned: (DERBY-195) isSearchable() returns true for a calculated field

[ http://issues.apache.org/jira/browse/DERBY-195?page=all ] Francois Orsini reassigned DERBY-195: - Assign To: Francois Orsini > isSearchable() returns true for a calculated field > -- > > Key:

[jira] Created: (DERBY-416) Parameter in one of the error messages is not replaced by the desired value.

Parameter in one of the error messages is not replaced by the desired value. Key: DERBY-416 URL: http://issues.apache.org/jira/browse/DERBY-416 Project: Derby Type: Bug Components: JDBC

[jira] Created: (DERBY-415) sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing

sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing -- Key: DERBY-415 URL: http://issues.apache.org/jira/browse/DERBY-415 P

Re: [jira] Updated: (DERBY-398) Exclude tests for J2ME/CDC/Foundation platform

Deepa Remesh (JIRA) wrote: > [ http://issues.apache.org/jira/browse/DERBY-398?page=all ] > > Deepa Remesh updated DERBY-398: > --- > > Attachment: derby-398.diff > derby-398.status > derbyall_report.txt > > This patch excludes

[jira] Commented: (DERBY-412) Connetion toString should show type information and the meaning of the identifier that it prints

[ http://issues.apache.org/jira/browse/DERBY-412?page=comments#action_12314718 ] Kathey Marsden commented on DERBY-412: -- Thanks David. Once you have a solidified a proposal for the different connection types, can you submit it to the community for vot

[jira] Updated: (DERBY-412) Connetion toString should show type information and the meaning of the identifier that it prints

[ http://issues.apache.org/jira/browse/DERBY-412?page=all ] Andrew McIntyre updated DERBY-412: -- Fix Version: (was: 10.1.1.0) Moving Fix In to 10.2. > Connetion toString should show type information and the meaning of the > identifier that it prin

[jira] Updated: (DERBY-383) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Tools and Utilities Guide

[ http://issues.apache.org/jira/browse/DERBY-383?page=all ] Jeff Levitt updated DERBY-383: -- Attachment: derby383.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby.

[jira] Assigned: (DERBY-412) Connetion toString should show type information and the meaning of the identifier that it prints

[ http://issues.apache.org/jira/browse/DERBY-412?page=all ] David Van Couvering reassigned DERBY-412: - Assign To: David Van Couvering It only makes sense for me to take this one :). Thanks for the format suggestion! > Connetion toString should

[jira] Updated: (DERBY-414) Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level

[ http://issues.apache.org/jira/browse/DERBY-414?page=all ] Kathey Marsden updated DERBY-414: - Attachment: deby414Repro.zip run repro as java TestDerbyNSXA > Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level > --

[jira] Created: (DERBY-414) Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level

Client XA has a problem with the TRANSACTION_READ_UNCOMMITTED isolation level - Key: DERBY-414 URL: http://issues.apache.org/jira/browse/DERBY-414 Project: Derby Type: Bug Components: Netwo

[jira] Created: (DERBY-413) Need an easy way to change the localhost string in the Netwrok server tests to test on a different sever (need for the Ipv6 Testing)

Need an easy way to change the localhost string in the Netwrok server tests to test on a different sever (need for the Ipv6 Testing) Key: DERBY-413

[jira] Created: (DERBY-412) Connetion toString should show type information and the meaning of the identifier that it prints

Connetion toString should show type information and the meaning of the identifier that it prints - Key: DERBY-412 URL: http://issues.apache.org/jira/browse/DERBY-412 Project: De

Re: Compile Issues

On Jun 29, 2005, at 2:45 PM, Daniel John Debrunner wrote: I thought Javacc (and other BSD jars) was in the build now. Included in Subversion, but not the source distributions for 10.0. For the 10.1 release, it will also be in the source distribution. andrew

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

ClientDataSource should not require serverName/portNumber to be set --- Key: DERBY-410 URL: http://issues.apache.org/jira/browse/DERBY-410 Project: Derby Type: Bug Versions: 10.1.1.0, 10.2.0.

[jira] Created: (DERBY-411) dblook_test fails on aix platform fails with ibmjdk131

dblook_test fails on aix platform fails with ibmjdk131 -- Key: DERBY-411 URL: http://issues.apache.org/jira/browse/DERBY-411 Project: Derby Type: Bug Components: Test Versions: 10.0.2.0 Environment: OS

Re: Compile Issues

Dave Jarvis wrote: > Hi, > > With ant for Java, projects should successfully compile using: > > tar zxf tarball-src.tar.gz > cd src > ant > > I have both J2SDK 1.4.2 and Apache Ant 1.6.5. Yet the instructions for > compiling Derby required such things as: > > adding a propertie

[jira] Commented: (DERBY-88) RunSuite summary rounds incorrectly

[ http://issues.apache.org/jira/browse/DERBY-88?page=comments#action_12314708 ] John Sisson commented on DERBY-88: -- FYI.. This problem still appears to be occuring on the 10.1 branch (svn ver 201931). > RunSuite summary rounds incorrectly > --

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

[ http://issues.apache.org/jira/browse/DERBY-409?page=comments#action_12314707 ] Kathey Marsden commented on DERBY-409: -- This issue would appear to be in java/client/org/apache/derby/client/am/Connection.java databaseName_ = dataSource.getDatabaseName

[jira] Commented: (DERBY-401) Add SQLException subclasses and throw them correctly to match JDBC 4 spec

[ http://issues.apache.org/jira/browse/DERBY-401?page=comments#action_12314706 ] Daniel John Debrunner commented on DERBY-401: - I agree, though I assume the description is the correct action, and not the Summary. I don't think derby needs to hav

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

[ http://issues.apache.org/jira/browse/DERBY-409?page=all ] Kathey Marsden updated DERBY-409: - Attachment: ConnectionAttributes.java repro > ClientDataSource setConnectionAttributes("create=true") fails with "An > attempt was made to access a databa

[jira] Updated: (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 ] John Sisson updated DERBY-407: -- Attachment: derbylang_report.txt derbylang_report.txt attached. > predicatesIntoViews test failure on slow machine in Derby 10.1 branch version > 201931 >

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

ClientDataSource setConnectionAttributes("create=true") fails with "An attempt was made to access a database, mydbcreate=true, which was not found." ---

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

[ http://issues.apache.org/jira/browse/DERBY-407?page=comments#action_12314703 ] John Sisson commented on DERBY-407: --- Mail from Myrna on derby-dev: Hi John, We've been seeing an intermittent failure with this test with some of the jvms we run against o

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

[ http://issues.apache.org/jira/browse/DERBY-407?page=comments#action_12314704 ] John Sisson commented on DERBY-407: --- Note that I wasn't running the derbyall suite, I was running derbylang. > predicatesIntoViews test failure on slow machine in Derby 10.1

[jira] Created: (DERBY-408) Fix formatting of syntax sections in manuals

Fix formatting of syntax sections in manuals Key: DERBY-408 URL: http://issues.apache.org/jira/browse/DERBY-408 Project: Derby Type: Bug Environment: all Reporter: Jeff Levitt Priority: Minor Fix For: 10.2.0.

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

predicatesIntoViews test failure on slow machine in Derby 10.1 branch version 201931 - Key: DERBY-407 URL: http://issues.apache.org/jira/browse/DERBY-407 Project: Derby Type: Test

[jira] Resolved: (DERBY-348) example.html file for the SimpleApp does not describe the arguments accepted by the program

[ http://issues.apache.org/jira/browse/DERBY-348?page=all ] Andrew McIntyre resolved DERBY-348: --- Fix Version: 10.1.1.0 Resolution: Fixed Committed to trunk with revision 202430. Will merge to 10.1 branch before release. > example.html file

[jira] Updated: (DERBY-381) Doc review (CLOSED TO FURTHER COMMENTS): Derby Server and Admin Guide

[ http://issues.apache.org/jira/browse/DERBY-381?page=all ] Jeff Levitt updated DERBY-381: -- Attachment: derby381.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derby

Re: [jira] Commented: (DERBY-348) example.html file for the SimpleApp does not describe the arguments accepted by the program

On Jun 29, 2005, at 1:20 PM, Jeff Levitt wrote: Thanks for mentioning that David, I saw that and thought that that was not something we want to happen. I forgot to mention it when I submitted the patch. I dont think there is a bug filed for it, and I wanted the doc to match the functionality

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

[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Kathey Marsden updated DERBY-406: - Version: 10.1.1.0 10.2.0.0 > Client DataSource should not require user property to be set > --

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

[ http://issues.apache.org/jira/browse/DERBY-406?page=all ] Kathey Marsden updated DERBY-406: - Attachment: DataSourceNoUser.java > Client DataSource should not require user property to be set >

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

Client DataSource should not require user property to be set Key: DERBY-406 URL: http://issues.apache.org/jira/browse/DERBY-406 Project: Derby Type: Bug Components: Network Client Versions: 10.1.1.0

[jira] Updated: (DERBY-264) This enhancement to allow expressions in ORDER BY clause will require documentation changes.

[ http://issues.apache.org/jira/browse/DERBY-264?page=all ] Andrew McIntyre updated DERBY-264: -- Fix Version: 10.2.0.0 (was: 10.1.1.0) Version: 10.2.0.0 Environment: Moving to 10.2 as it appears no one is currently worki

[jira] Resolved: (DERBY-97) Support J2ME/CDC/Foundation with JSR169 JDBC subset

[ http://issues.apache.org/jira/browse/DERBY-97?page=all ] Daniel John Debrunner resolved DERBY-97: Resolution: Fixed JSR functionality for 10.1 is complete. sub-tasks can be added to further work. > Support J2ME/CDC/Foundation with JSR169

[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 ] Andrew McIntyre updated DERBY-375: -- Fix Version: 10.2.0.0 (was: 10.1.1.0) Version: 10.2.0.0 Moving to 10.2 > Specification of incomplete server properties on comma

[jira] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.

[ http://issues.apache.org/jira/browse/DERBY-374?page=all ] Andrew McIntyre updated DERBY-374: -- Fix Version: 10.2.0.0 (was: 10.1.1.0) Version: 10.2.0.0 Moving to 10.2. > Invalid URL with Derby Client when connecting to Netw

[jira] Commented: (DERBY-381) Doc review (CLOSED TO FURTHER COMMENTS): Derby Server and Admin Guide

[ http://issues.apache.org/jira/browse/DERBY-381?page=comments#action_12314693 ] Andrew McIntyre commented on DERBY-381: --- For the record, regarding item #8 of Susan Cline's comments, I do plan to compile the demo classes and include them in the -bin d

[jira] Created: (DERBY-405) SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables

SYNONYM should not be allowed in SESSION schema because that can confusion wih temporary tables --- Key: DERBY-405 URL: http://issues.apache.org/jira/browse/DERBY-405 Project: Derby

[jira] Commented: (DERBY-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual

[ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314692 ] Andrew McIntyre commented on DERBY-382: --- Please add a note concerning DERBY-254 to the section regarding SQLStates. Here's the DERBY-254 description: SQLExceptions gener

[jira] Updated: (DERBY-254) SQLStates for SQLExceptions thrown from the client should not be null and should match embedded where possible

[ http://issues.apache.org/jira/browse/DERBY-254?page=all ] Andrew McIntyre updated DERBY-254: -- Fix Version: 10.2.0.0 (was: 10.1.1.0) Description: SQLExceptions generated from the client tend to have a null SQLState. An evalua

[jira] Assigned: (DERBY-390) Import/export fails with table names that are quoted in SQL like import to table "Order"

[ http://issues.apache.org/jira/browse/DERBY-390?page=all ] Suresh Thalamati reassigned DERBY-390: -- Assign To: Suresh Thalamati > Import/export fails with table names that are quoted in SQL like import > to table "Order" > ---

Re: [jira] Commented: (DERBY-348) example.html file for the SimpleApp does not describe the arguments accepted by the program

--- "David Van Couvering (JIRA)" wrote: > [ > http://issues.apache.org/jira/browse/DERBY-348?page=comments#action_12314690 > ] > > David Van Couvering commented on DERBY-348: > --- > > Hi, Jeff, I took at look at this, looks good. +1. > It's too

Compile Issues

Hi, With ant for Java, projects should successfully compile using: tar zxf tarball-src.tar.gz cd src ant I have both J2SDK 1.4.2 and Apache Ant 1.6.5. Yet the instructions for compiling Derby required such things as: adding a properties file to my home directo

[jira] Commented: (DERBY-348) example.html file for the SimpleApp does not describe the arguments accepted by the program

[ http://issues.apache.org/jira/browse/DERBY-348?page=comments#action_12314690 ] David Van Couvering commented on DERBY-348: --- Hi, Jeff, I took at look at this, looks good. +1. It's too bad the sysinfo tools complains about missing DB2 client jar

Re: Code coverage for 10.1.1.0 candidate

Code coverage was run on release10.1.1.0 and build number 190628. > Ramandeep Kaur wrote: > > > Hi, > > > > I ran code coverage for 10.1.1.0 candidate and the results are as > > following: > > > > EMMA Coverage Report (generated Fri Jun 24 17:56:25 PDT 2005)

Re: Code coverage for 10.1.1.0 candidate

Hi, I have code coverage results with links to Source code files that shows which classes/methods/blocks/lines were covered during the testing. There are about 1200 files. I am looking into some options to make the files available to community. Will make it available soon. Thanks, Raman On

[jira] Assigned: (DERBY-404) org.apache.derby.iapi.store.access.RowUtil.isRowEmpty has (never exercised) bug

[ http://issues.apache.org/jira/browse/DERBY-404?page=all ] Daniel John Debrunner reassigned DERBY-404: --- Assign To: Daniel John Debrunner > org.apache.derby.iapi.store.access.RowUtil.isRowEmpty has (never exercised) > bug > ---

[jira] Created: (DERBY-404) org.apache.derby.iapi.store.access.RowUtil.isRowEmpty has (never exercised) bug

org.apache.derby.iapi.store.access.RowUtil.isRowEmpty has (never exercised) bug --- Key: DERBY-404 URL: http://issues.apache.org/jira/browse/DERBY-404 Project: Derby Type: Bug Components: S

Re: [jira] Commented: (DERBY-31) Statement.setQueryTimeout() support.

Daniel John Debrunner wrote: > Daniel John Debrunner wrote: > > >>[EMAIL PROTECTED] wrote: >> >>[on comments about re-use of TimerTasks] >> write a comment about this in the code in a subsequent >> >> >>>patch (for instance when implementing Statement.cancel), unless anybody >>>wants me to addre

[jira] Updated: (DERBY-398) Exclude tests for J2ME/CDC/Foundation platform

[ http://issues.apache.org/jira/browse/DERBY-398?page=all ] Deepa Remesh updated DERBY-398: --- Attachment: derby-398.diff derby-398.status derbyall_report.txt This patch excludes tests and suites which are expected to fail wit

Re: DERBY-213 Early patch

Philip Wilder wrote: > I've attached an "alpha" patch for the DERBY-213 for anyone who is > interested in the DERBY-213 issue. It should be noted that the patch is > contingent upon our current interpretation of the JDBC > specifications/documentation. Did we come to a resolution on your document

Re: Code coverage for 10.1.1.0 candidate

Ramandeep Kaur wrote: > Hi, > > I ran code coverage for 10.1.1.0 candidate and the results are as > following: > > EMMA Coverage Report (generated Fri Jun 24 17:56:25 PDT 2005) > > OVERALL COVERAGE SUMMARY > Class % -- 89% (1062/1188) > Method % --- 73% (14688/20201) > Block % ---

Re: [jira] Commented: (DERBY-31) Statement.setQueryTimeout() support.

Daniel John Debrunner wrote: > [EMAIL PROTECTED] wrote: > > [on comments about re-use of TimerTasks] > write a comment about this in the code in a subsequent > >>patch (for instance when implementing Statement.cancel), unless anybody >>wants me to address this now and submit a new patch. > >

Re: Question regarding predicatesIntoViews test failure in Derby 10.1 branch version 201931

Hi John,   We've been seeing an intermittent failure with this test with some of the jvms we run against on a slow machine. It appears the test is not 'tight' enough to always pass on slower machines - sometimes one of the queries results in a table scan, sometimes an index scan. I can't right now

DERBY-213 Early patch

I've attached an "alpha" patch for the DERBY-213 for anyone who is interested in the DERBY-213 issue. It should be noted that the patch is contingent upon our current interpretation of the JDBC specifications/documentation. This patch is meant to address both the early close problem recently di

[jira] Closed: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row

[ http://issues.apache.org/jira/browse/DERBY-403?page=all ] Bernt M. Johnsen closed DERBY-403: -- Resolution: Duplicate Duplicate of DERBY-213 > NetworkClient closes resultset when next() moves the cursor beyond the last > row > ---

[jira] Commented: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row

[ http://issues.apache.org/jira/browse/DERBY-403?page=comments#action_12314675 ] Kathey Marsden commented on DERBY-403: -- This is a duplicate of DERBY-213 which Philip Wilder and I have been working on. Removing that close means that client has to be c

[jira] Updated: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row

[ http://issues.apache.org/jira/browse/DERBY-403?page=all ] Bernt M. Johnsen updated DERBY-403: --- Description: NetworkClient closes resultset when next() moves the cursor beyond the last row The following stub will work in EmbeddedDriver but not in Net

[jira] Created: (DERBY-403) NetworkClient closes resultset when next() moves the cursor beyond the last row

NetworkClient closes resultset when next() moves the cursor beyond the last row --- Key: DERBY-403 URL: http://issues.apache.org/jira/browse/DERBY-403 Project: Derby Type: Bug Components: N

Re: [jira] Updated: (DERBY-397) Make it sure for the connection to be closed in drda.Database#close() even if Exception happens in conn.rollback().

Hello Kathy. Kathey wrote: In Derby when you close a connection, the close will fail if there is an active transaction, so the rollback is needed to allow the connection to close properly. Yes, there is a history which is that the rollback was not needed on connection close in a previous incar

[jira] Updated: (DERBY-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby

[ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: -- Attachment: derby379.diff Re-attaching patch...had some problems with the initial attachment process because of my connection... > Doc review (CLOSED TO FURTHER CO

[jira] Updated: (DERBY-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby

[ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: -- Attachment: derby379.diff The attached patch makes the changes requested in this doc review. I have created sample output on my own site: HTML files: http://derb