[jira] Updated: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1421?page=all ] Fernanda Pizzorno updated DERBY-1421: - Attachment: derby-1421.diff derby-1421.stat ResultSet.updateBinaryStream() fails for scrollable updatable result sets because of a

[jira] Updated: (DERBY-1421) ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

[ http://issues.apache.org/jira/browse/DERBY-1421?page=all ] Fernanda Pizzorno updated DERBY-1421: - Version: 10.2.0.0 Derby Info: [Patch Available] ResultSet.updateBinaryStream fails when the result type is TYPE_SCROLL_INSENSITIVE

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12417059 ] Andreas Korneliussen commented on DERBY-1361: - For the scrollable case, I found two problems: 1. The network client will do a parsing of the SQL and reposition

[jira] Commented: (DERBY-528) Support for DRDA Strong User ID and Password Substitute Authentication (USRSSBPWD) scheme

[ http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12417060 ] Bernt M. Johnsen commented on DERBY-528: EncryptionManager (this applies DecryptionManager) actually implements two distinct objects in your patch, only distinguished

Regression Test Failure! - Derby 415736 - Sun DBTG

[Auto-generated mail] *Derby* 415736/2006-06-20 19:46:07 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 15715700 0 106.33% SunOS-5.10_i86pc-i386 Details in

[jira] Created: (DERBY-1433) Client driver does not handle string literals containing where current of correctly

Client driver does not handle string literals containing where current of correctly - Key: DERBY-1433 URL: http://issues.apache.org/jira/browse/DERBY-1433 Project: Derby Type: Bug

[jira] Updated: (DERBY-1433) Client driver does not handle string literals containing where current of correctly

[ http://issues.apache.org/jira/browse/DERBY-1433?page=all ] Knut Anders Hatlen updated DERBY-1433: -- Attachment: cursor.java Attached a repro for the bug (cursor.java). When the program is run, it is supposed to print Writing where current of in

Re: [jira] Commented: (DERBY-1431) Typo in link to Simple Example from frameworks/readme.html

Stan Bradbury (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1431?page=comments#action_12417004 ] Stan Bradbury commented on DERBY-1431: -- I like to plan for success. To me that means, in this case, many more demo programs, databases,

[jira] Commented: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=comments#action_12417072 ] Andreas Korneliussen commented on DERBY-1361: - BTW, this is what SQL foundation, part 2, 4.29 Cursors, says about this situation: A holdable cursor that has been

[jira] Updated: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen updated DERBY-137: - Attachment: derby-137-v1.diff derby-137-v1.stat The attached patch changes the data types and adds missing columns so that the result

[jira] Updated: (DERBY-137) Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result sets are required.

[ http://issues.apache.org/jira/browse/DERBY-137?page=all ] Knut Anders Hatlen updated DERBY-137: - Derby Info: [Patch Available] Patch is available and ready for review. Thanks! Derby metadata always returns JDBC 2 result sets, even when JDBC 3

[jira] Commented: (DERBY-1314) Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()

[ http://issues.apache.org/jira/browse/DERBY-1314?page=comments#action_12417104 ] Knut Anders Hatlen commented on DERBY-1314: --- Does anyone have comments to the patch? If not, I plan to commit in a couple of days. Differences between client and

Re: Sun DBTG testing for 10.1.3.0 - Results

We have run a testcycle on 10.1.3.0 with tests as specified below on platforms as specified below. We did NOT discover any regressions and we did NOT see any new failures. All tests were run with both Sun jvm 1.5.0 and Sun jvm 1.4.2 Tests/testsuites run: demo derbyall derbylang

Re: test harness and jvmoptions

Vemund Ostgaard wrote: Myrna van Lunteren wrote: :-( The jvmflag passing is broken (not sure how well it ever worked). See also DERBY-1091. I intend to work on that this week...But it's a big can of worms. But try without the quotes... I looked a little at this code, and RunTest, RunList

[jira] Updated: (DERBY-1183) Client java.sql.ResultSet.getCursorName() does not return the correct cursor name for Statements after the first execution

[ http://issues.apache.org/jira/browse/DERBY-1183?page=all ] Dag H. Wanvik updated DERBY-1183: - Attachment: derby-1183-2.stat derby-1183-2.diff Not sure what happened, anyway here is a new version of the patch which passes derbyall.

[jira] Updated: (DERBY-1361) positioned updates and deletes allowed after a commit without repositioning the cursor - if the table is indexed on the columns selected

[ http://issues.apache.org/jira/browse/DERBY-1361?page=all ] Andreas Korneliussen updated DERBY-1361: Attachment: DERBY-1361.diff DERBY-1361.stat Attaching a patch for this issue. The patch (DERBY-1361.diff + stat) does the

[jira] Resolved: (DERBY-1338) Client tests DerbyNetNewServer and NSinSameVM fail with NoClassDefFoundError: DRDAProtocolExceptionInfo when run from classes dir

[ http://issues.apache.org/jira/browse/DERBY-1338?page=all ] Bryan Pendleton resolved DERBY-1338: Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks for the patch, Dag! In addition to your testing, derbynetclientmats runs clean

[jira] Closed: (DERBY-1413) SQL State STORE_XA_XAER_DUPID does not have a matching message

[ http://issues.apache.org/jira/browse/DERBY-1413?page=all ] David Van Couvering closed DERBY-1413: -- Resolution: Invalid The problem was that there is a SQLState XASX1 and a SQL State XASX1.S in SQLState.java. missed this when I reported

Re: test harness and jvmoptions

On 6/21/06, Vemund Ostgaard [EMAIL PROTECTED] wrote: Vemund Ostgaard wrote: Myrna van Lunteren wrote: :-( The jvmflag passing is broken (not sure how well it ever worked). See also DERBY-1091. I intend to work on that this week...But it's a big can of worms. But try without the

[jira] Resolved: (DERBY-1420) Make JitTest.java independent of Derby release

[ http://issues.apache.org/jira/browse/DERBY-1420?page=all ] Mamta A. Satoor resolved DERBY-1420: Fix Version: 10.1.3.1 10.1.4.0 10.2.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) The

[jira] Closed: (DERBY-1420) Make JitTest.java independent of Derby release

[ http://issues.apache.org/jira/browse/DERBY-1420?page=all ] Mamta A. Satoor closed DERBY-1420: -- Make JitTest.java independent of Derby release -- Key: DERBY-1420 URL:

JIRA Developer Access

Hi, I'm a Google SoC student working on adding a new LRU Cache Manager to Derby. May I get developer access to JIRA? Thanks, Gokul

Re: JIRA Developer Access

On 6/21/06, Gokul Soundararajan [EMAIL PROTECTED] wrote: Hi, I'm a Google SoC student working on adding a new LRU Cache Manager to Derby. May I get developer access to JIRA? Granted. Welcome to Derby! andrew

[jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

[ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_copyrights.diff Attaching derby-1271_copyrights.diff. This adjusts dates in the visible copyright notices in the user guides. Touches

Re: [jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

A B (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416921 ] A B commented on DERBY-1108: 3) The test is not ok. To test what it wants to test, that we can't change the isolation in the middle of retrieving results

Re: [PRE-VOTE DISCUSSION] Compatibility rules and interface table

Hi David, I had a couple more comments on the compatibility commitments. Cheers-Rick - Changes to stored procedures: We will have to change column order if we add Derby-specific columns to a metadata ResultSet and then a later JDBC also adds more columns. - Changes to Database Tables: We

Re: [PRE-VOTE DISCUSSION] Compatibility rules and interface table

hi guys Rick Hillegas wrote: Hi David, I had a couple more comments on the compatibility commitments. Cheers-Rick - Changes to stored procedures: We will have to change column order if we add Derby-specific columns to a metadata ResultSet and then a later JDBC also adds more columns.

[jira] Updated: (DERBY-551) Allow invoking java stored procedures from inside a trigger. Make CALL a valid statement in the trigger body.

[ http://issues.apache.org/jira/browse/DERBY-551?page=all ] Deepa Remesh updated DERBY-551: --- Fix Version: 10.2.0.0 Assign To: Deepa Remesh Allow invoking java stored procedures from inside a trigger. Make CALL a valid statement in the trigger

Re: [PRE-VOTE DISCUSSION] Compatibility rules and interface table

Good news Lance, thanks, I was getting worried if we were going to have to regularly change column order and break existing applications/IDEs/etc. David Lance J. Andersen wrote: hi guys Rick Hillegas wrote: Hi David, I had a couple more comments on the compatibility commitments.

[jira] Assigned: (DERBY-1394) Working With Derby - Introduction and prerequisites - Improvements

[ http://issues.apache.org/jira/browse/DERBY-1394?page=all ] Halley Pacheco de Oliveira reassigned DERBY-1394: - Assign To: Halley Pacheco de Oliveira Working With Derby - Introduction and prerequisites - Improvements

Re: [PRE-VOTE DISCUSSION] Compatibility rules and interface table

Rick Hillegas wrote: Hi David, I had a couple more comments on the compatibility commitments. Cheers-Rick - Changes to stored procedures: We will have to change column order if we add Derby-specific columns to a metadata ResultSet and then a later JDBC also adds more columns. See

[jira] Commented: (DERBY-1394) Working With Derby - Introduction and prerequisites - Improvements

[ http://issues.apache.org/jira/browse/DERBY-1394?page=comments#action_12417191 ] Halley Pacheco de Oliveira commented on DERBY-1394: --- Hi Stan, I'm glad that you liked the changes and the reference to the Owl English site. I committed

[jira] Closed: (DERBY-1394) Working With Derby - Introduction and prerequisites - Improvements

[ http://issues.apache.org/jira/browse/DERBY-1394?page=all ] Halley Pacheco de Oliveira closed DERBY-1394: - Resolution: Fixed Working With Derby - Introduction and prerequisites - Improvements

[jira] Closed: (DERBY-1287) Derby Server and Administration Guide - Network client driver examples should show how to enable authentication

[ http://issues.apache.org/jira/browse/DERBY-1287?page=all ] Halley Pacheco de Oliveira closed DERBY-1287: - Derby Server and Administration Guide - Network client driver examples should show how to enable authentication

[jira] Closed: (DERBY-1270) pt_BR translation DTD directory (../dtd/ - ../../dtd/)

[ http://issues.apache.org/jira/browse/DERBY-1270?page=all ] Halley Pacheco de Oliveira closed DERBY-1270: - Assign To: Halley Pacheco de Oliveira pt_BR translation DTD directory (../dtd/ - ../../dtd/)

[jira] Closed: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

[ http://issues.apache.org/jira/browse/DERBY-1263?page=all ] Halley Pacheco de Oliveira closed DERBY-1263: - build.xml doesn't create the ${basedir}/src/dtd directory ---

Re: [PRE-VOTE DISCUSSION] Compatibility rules and interface table

David Van Couvering wrote: Good news Lance, thanks, I was getting worried if we were going to have to regularly change column order and break existing applications/IDEs/etc. Hopefully we don't have any documented Derby specific additional columns in the metadata, that would be non-standard.

[jira] Closed: (DERBY-1200) Derby Server and Administration Guide - Managing the Derby Network Server remotely by using the servlet interface

[ http://issues.apache.org/jira/browse/DERBY-1200?page=all ] Halley Pacheco de Oliveira closed DERBY-1200: - Derby Server and Administration Guide - Managing the Derby Network Server remotely by using the servlet interface

[jira] Commented: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)

[ http://issues.apache.org/jira/browse/DERBY-1373?page=comments#action_12417195 ] Sunitha Kambhampati commented on DERBY-1373: Thanks Mathias for finding this issue and posting a patch. It would be nice if you could add some tests so we dont

[jira] Updated: (DERBY-803) derbynet/DerbyNetAutoStart.java test fails intermittently with org.apache.derby.iapi.services.context.ShutdownException

[ http://issues.apache.org/jira/browse/DERBY-803?page=all ] Deepa Remesh updated DERBY-803: --- Assign To: (was: Deepa Remesh) Of late, I see this intermittent test failure is reported by few people. However, I have not been able to repro this issue on

[jira] Created: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

Client can send incorrect database name to server after having made multiple connections to different databases. Key: DERBY-1434 URL:

[jira] Updated: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=all ] A B updated DERBY-1434: --- Attachment: d1434.java _driver_1 Server2.trace Attaching a simple repro of the problem. To run, start the server with tracing on: java

ADVICE REQUESTED: Fixing MessageBundleTest

So, as Andrew very astutely pointed out, i18n/MessageBundleTest.java will not succeed when running against the jar files because it tries to load shared/common/reference/SQLState, which is not included in the jar files. This problem also exists for MessageId.java, which this test also refers

[jira] Assigned: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ] Manjula Kutty reassigned DERBY-1108: Assign To: Manjula Kutty The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[jira] Commented: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12417208 ] Manjula Kutty commented on DERBY-1108: -- I have made a patch with the rs.next after the setTransactionIsolation and the test passes with both ibm1.5 and sun jdk1.5.

[jira] Updated: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ] Manjula Kutty updated DERBY-1108: - Attachment: svn_diff_06_21.txt The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[jira] Updated: (DERBY-1108) The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

[ http://issues.apache.org/jira/browse/DERBY-1108?page=all ] Manjula Kutty updated DERBY-1108: - Attachment: svn_stat_06_21.txt The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5

Re: [jira] Updated: (DERBY-1271) Release documentation for JDBC4 release

Rick Hillegas (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1271?page=all ] Rick Hillegas updated DERBY-1271: - Attachment: derby-1271_copyrights.diff Attaching derby-1271_copyrights.diff. This adjusts dates in the visible

[jira] Resolved: (DERBY-851) Remove org.apache.derby.client.resource package - no longer needed

[ http://issues.apache.org/jira/browse/DERBY-851?page=all ] David Van Couvering resolved DERBY-851: --- Resolution: Fixed Remove org.apache.derby.client.resource package - no longer needed

[jira] Resolved: (DERBY-1349) Document user-visible changes affected by internationalization of the network client

[ http://issues.apache.org/jira/browse/DERBY-1349?page=all ] David Van Couvering resolved DERBY-1349: Resolution: Fixed Closing this bug, being tracked by DERBY-254 Document user-visible changes affected by internationalization of the

[jira] Resolved: (DERBY-400) Network client message strings not internationalized

[ http://issues.apache.org/jira/browse/DERBY-400?page=all ] David Van Couvering resolved DERBY-400: --- Resolution: Fixed Resolved, all sub-tasks completed. Network client message strings not internationalized

[jira] Created: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger Key: DERBY-1435 URL: http://issues.apache.org/jira/browse/DERBY-1435

Re: ADVICE REQUESTED: Fixing MessageBundleTest

David Van Couvering wrote: So, as Andrew very astutely pointed out, i18n/MessageBundleTest.java will not succeed when running against the jar files because it tries to load shared/common/reference/SQLState, which is not included in the jar files. This problem also exists for MessageId.java,

Re: ADVICE REQUESTED: Fixing MessageBundleTest

Hm, a build-time check. I guess in a way it is a build-time issue. Let me think about how I might do that, thanks for the idea. David Daniel John Debrunner wrote: David Van Couvering wrote: So, as Andrew very astutely pointed out, i18n/MessageBundleTest.java will not succeed when running

[jira] Updated: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[ http://issues.apache.org/jira/browse/DERBY-1435?page=all ] Deepa Remesh updated DERBY-1435: Attachment: repro1435.sql Attaching a sql script 'repro1435.sql' to repro this issue Conglomerate does not exist occurs in a specific case after dropping a

[jira] Commented: (DERBY-1395) Change the client SQLState to match that of embedded for the exception thrown on a closed statement whose connection is also closed

[ http://issues.apache.org/jira/browse/DERBY-1395?page=comments#action_12417215 ] David Van Couvering commented on DERBY-1395: Deepa, is there a particular test that exemplifies this behavior? I could poke around but if there are existing

[jira] Commented: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[ http://issues.apache.org/jira/browse/DERBY-1435?page=comments#action_12417226 ] Suresh Thalamati commented on DERBY-1435: - Good catch deepa. My guess is the plans in the statement cache are not getting invalidated corretcly when table t1 is

[jira] Updated: (DERBY-1435) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

[ http://issues.apache.org/jira/browse/DERBY-1435?page=all ] Suresh Thalamati updated DERBY-1435: Component: SQL (was: Store) Conglomerate does not exist occurs in a specific case after dropping a table referenced by a trigger

MySQL to Derby Migration Tool

Hello, I am a Google Summer of code participant working on the Derby Migration tool project. The High level design document is posted at http://wiki.apache.org/db-derby/MysqlDerbyMigration/DesignDocument There are 2 approaches described in the document -- one based on the use DatabaseMetaData

[jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12417238 ] Kathey Marsden commented on DERBY-1434: --- A USER SYMPTOM I see that if our table in the first database has more data than can be retrieved in one QRYDTA this can cause

[jira] Updated: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

[ http://issues.apache.org/jira/browse/DERBY-1434?page=all ] Kathey Marsden updated DERBY-1434: -- Priority: Major (was: Minor) Raising this to major as it can cause premature closing of the result set. and statement. Client can send incorrect

Re: [jira] Commented: (DERBY-1434) Client can send incorrect database name to server after having made multiple connections to different databases.

Kathey Marsden (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12417238 ] Kathey Marsden commented on DERBY-1434: --- A USER SYMPTOM I see that if our table in the first database has more data than can be retrieved

Re: [VOTE] 10.1.3.0 release

On 6/20/06, Kathey Marsden [EMAIL PROTECTED] wrote: Mike Matrigali wrote: I would like to see the fix for DERBY-1392 included in the 10.1.3 release if there is a second release candidate. While the bug is an edge error case, the result is a corrupt db. I believe there is little risk as