[jira] Updated: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ] Bernt M. Johnsen updated DERBY-1231: Attachment: DERBY-1231-v2.diff New version. Ready for commit. LIKE does not match empty strings when used with a prepared statement

[jira] Created: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

checkDataSource and checkDataSource30 fail in the tinderbox test Key: DERBY-2155 URL: http://issues.apache.org/jira/browse/DERBY-2155 Project: Derby Issue Type: Bug

[jira] Assigned: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen reassigned DERBY-2155: - Assignee: Knut Anders Hatlen checkDataSource and checkDataSource30 fail in the tinderbox test

[jira] Updated: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen updated DERBY-2155: -- Attachment: derby-2155.diff derby-2155.stat The attached patch updates the master files so that the tests run cleanly. It also

[jira] Resolved: (DERBY-2155) checkDataSource and checkDataSource30 fail in the tinderbox test

[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ] Knut Anders Hatlen resolved DERBY-2155. --- Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 482972. checkDataSource and checkDataSource30 fail in the tinderbox test

[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_12455931 ] Knut Anders Hatlen commented on DERBY-1434: --- This fix cannot be merged to 10.2 automatically because it depends on some changes to the JUnit framework

[jira] Commented: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455934 ] Knut Anders Hatlen commented on DERBY-1231: --- Looks good, +1 to commit. You could also remove NOTE: This may be null if the pattern is an empty string.

[jira] Updated: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ] Bernt M. Johnsen updated DERBY-1231: Attachment: DERBY-1231-v3.diff Thanks Knut. Here's the final patch LIKE does not match empty strings when used with a prepared statement

[jira] Resolved: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ] Bernt M. Johnsen resolved DERBY-1231. - Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed revision 482983. LIKE does not match

[jira] Reopened: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ] Bernt M. Johnsen reopened DERBY-1231: - Merge to 10.2 LIKE does not match empty strings when used with a prepared statement

[jira] Assigned: (DERBY-2147) LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ] Bernt M. Johnsen reassigned DERBY-2147: --- Assignee: Bernt M. Johnsen LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

[jira] Commented: (DERBY-2147) LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

[ http://issues.apache.org/jira/browse/DERBY-2147?page=comments#action_12455954 ] Bernt M. Johnsen commented on DERBY-2147: - The same applies to the escape character which is caught by: // escape cannot be a column

Derby Client Driver and LOBs

Hi, I'm a developer in the Apache Jackrabbit project and in the process of making it clusterable we're facing some serious problem: we have all nodes in the cluster share the repository data and are using derby as database back end, running standalone. When retrieving large binary data through

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12455972 ] Tomohito Nakayama commented on DERBY-1471: -- I will wait for days and will commit the patch ... Implement layer B streaming for new methods defined in

[jira] Commented: (DERBY-2146) Translate Getting Started with Derby to Japanese

[ http://issues.apache.org/jira/browse/DERBY-2146?page=comments#action_12455973 ] Tomohito Nakayama commented on DERBY-2146: -- Thank you Laura :) I think I could understoodd all of the manual. If you know improvement on this manual

[jira] Resolved: (DERBY-1231) LIKE does not match empty strings when used with a prepared statement

[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ] Bernt M. Johnsen resolved DERBY-1231. - Resolution: Fixed Committed revision 483042. LIKE does not match empty strings when used with a prepared statement

[jira] Updated: (DERBY-2147) LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ] Bernt M. Johnsen updated DERBY-2147: Attachment: DERBY-2147.diff DERBY-2147.stat Removed the two tests that disables this functionality. Updated master for

[jira] Updated: (DERBY-2147) LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ] Bernt M. Johnsen updated DERBY-2147: Derby Info: [Patch Available] LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)

Should be a statement with error allowed to do a rollback of the active transaction

Hi Saurabh, Correct, at this point the transaction is not committed, this only gets committed by the next select statement. Not only select statement but any other statement... ;-) Well the writeLocalRollback_() method calls buildRDBRLLBCK() and sends RDBRLLBCK code-point. I am not sure that

Re: Releasing latches when waiting for locks. When and why?

Knut Anders Hatlen wrote: Mike Matrigali [EMAIL PROTECTED] writes: One approach would be to continue to support the latching in the lockmanager, but to provide an alternate implementation using the same interfaces (or new interfaces if necessary). Then make the default module

[jira] Updated: (DERBY-2146) Translate Getting Started with Derby to Japanese

[ http://issues.apache.org/jira/browse/DERBY-2146?page=all ] Tomohito Nakayama updated DERBY-2146: - Attachment: DERBY-2146_2.patch DERBY-2146_2.status * Description of the patch * Add Japanese translated Getting Started with Derby

Re: Should be a statement with error allowed to do a rollback of the active transaction

Julius Stroffek [EMAIL PROTECTED] writes: Hi Saurabh, Correct, at this point the transaction is not committed, this only gets committed by the next select statement. Not only select statement but any other statement... ;-) Well the writeLocalRollback_() method calls buildRDBRLLBCK() and

Re: Re: build error ?

Thanks, Andrew. I am doing a sync right now. Will post how the build goes after that. thanks, Mamta On 12/5/06, Andrew McIntyre [EMAIL PROTECTED] wrote: On 12/5/06, Mamta Satoor [EMAIL PROTECTED] wrote: ok. I have the fix in my codeline for a long time now, but everytime I try to compile,

Re: Issues marked for fix in 10.2.2 in JIRA

Hi Rajesh, Thanks for bringing up this topic. I have created a new Derby version in JIRA, 10.2.3.0. I think we can reassign most of these issues to 10.2.3.0. Regards, -Rick Rajesh Kartha wrote: Hi, I noticed in JIRA there are about 87 issues marked for fix in 10.2.2, Here is a filter to

[jira] Updated: (DERBY-2134) Add long running System test for Derby

[ http://issues.apache.org/jira/browse/DERBY-2134?page=all ] Rick Hillegas updated DERBY-2134: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Add long running System test for Derby

[jira] Updated: (DERBY-2127) Hard coded words in the messages which will not get translated in other languages

[ http://issues.apache.org/jira/browse/DERBY-2127?page=all ] Rick Hillegas updated DERBY-2127: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Hard coded words in the messages which will not get translated in

[jira] Updated: (DERBY-1992) Upgrade to DITA Open Toolkit version 1.3

[ http://issues.apache.org/jira/browse/DERBY-1992?page=all ] Rick Hillegas updated DERBY-1992: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Upgrade to DITA Open Toolkit version 1.3

[jira] Updated: (DERBY-1946) Internal language transformations - explain why users should rewrite their queries

[ http://issues.apache.org/jira/browse/DERBY-1946?page=all ] Rick Hillegas updated DERBY-1946: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Internal language transformations - explain why users should

[jira] Updated: (DERBY-1934) Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions

[ http://issues.apache.org/jira/browse/DERBY-1934?page=all ] Rick Hillegas updated DERBY-1934: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Reference Manual updates - J2EE Compliance: Java Transaction API

[jira] Updated: (DERBY-1933) Reference Manual updates - Setting attributes for the db connection URL

[ http://issues.apache.org/jira/browse/DERBY-1933?page=all ] Rick Hillegas updated DERBY-1933: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Reference Manual updates - Setting attributes for the db connection

[jira] Updated: (DERBY-1932) Reference Manual updates - JDBC Reference section

[ http://issues.apache.org/jira/browse/DERBY-1932?page=all ] Rick Hillegas updated DERBY-1932: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassigning to 10.2.3.0. Reference Manual updates - JDBC Reference section

[jira] Resolved: (DERBY-1921) Bring STATUS file up to date

[ http://issues.apache.org/jira/browse/DERBY-1921?page=all ] Rick Hillegas resolved DERBY-1921. -- Resolution: Fixed Bring STATUS file up to date Key: DERBY-1921 URL:

[jira] Closed: (DERBY-1921) Bring STATUS file up to date

[ http://issues.apache.org/jira/browse/DERBY-1921?page=all ] Rick Hillegas closed DERBY-1921. Bring STATUS file up to date Key: DERBY-1921 URL: http://issues.apache.org/jira/browse/DERBY-1921

[jira] Updated: (DERBY-1920) DOCS - Improve topic titles for vague and duplicate topics

[ http://issues.apache.org/jira/browse/DERBY-1920?page=all ] Rick Hillegas updated DERBY-1920: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Reassign to 10.2.3.0. DOCS - Improve topic titles for vague and duplicate topics

[jira] Updated: (DERBY-1868) Merge argument descriptors into SQLState strings so that SQLState documentation can be generated by a program

[ http://issues.apache.org/jira/browse/DERBY-1868?page=all ] Rick Hillegas updated DERBY-1868: - Fix Version/s: 10.3.0.0 (was: 10.2.2.0) Reassigning to 10.3 since that's where the work will show up. Merge argument descriptors

Re: Derby Client Driver and LOBs

Hello. I'm afraid that your case is not addressed yet ... Several improvement around memory usage for LOB was achieved / is under work. But I think memory usage in NetworkClient driver when receiving LOB from NetworkServer is not improved yet. If you don't mind, could you tell us your case

[jira] Updated: (DERBY-1807) Run more grant/revoke tests on an upgraded database

[ http://issues.apache.org/jira/browse/DERBY-1807?page=all ] Rick Hillegas updated DERBY-1807: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Run more grant/revoke tests on an upgraded database

[jira] Updated: (DERBY-1806) Connection errors in 10.2.1.1 - not seen in 10.1.2.1

[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ] Rick Hillegas updated DERBY-1806: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Connection errors in 10.2.1.1 - not seen in 10.1.2.1

[jira] Updated: (DERBY-1801) Reoccurrence of JIRA-937: Instability in wisconsin test

[ http://issues.apache.org/jira/browse/DERBY-1801?page=all ] Rick Hillegas updated DERBY-1801: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Reoccurrence of JIRA-937: Instability in wisconsin test

[jira] Updated: (DERBY-1792) Have the buildjars target layut the jars identically to a distribution, with test and lib folders.

[ http://issues.apache.org/jira/browse/DERBY-1792?page=all ] Rick Hillegas updated DERBY-1792: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Have the buildjars target layut the jars identically to a distribution,

Re: Re: build error ?

The build does not give any errors after the import SanityManager checkin. Thanks, Andrew. I still don't understand why I was getting class file has wrong version 50.0, should be 48.0 rather than the real compilation error. thanks, Mamta On 12/6/06, Mamta Satoor [EMAIL PROTECTED] wrote:

[jira] Updated: (DERBY-1740) Change error message to indicate encryptionkey length to be atleast 16 characters instead of 8 characters

[ http://issues.apache.org/jira/browse/DERBY-1740?page=all ] Rick Hillegas updated DERBY-1740: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Change error message to indicate encryptionkey length to be atleast 16

[jira] Updated: (DERBY-1709) Deprecate scripts in frameworks directory

[ http://issues.apache.org/jira/browse/DERBY-1709?page=all ] Rick Hillegas updated DERBY-1709: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Deprecate scripts in frameworks directory

[jira] Updated: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

[ http://issues.apache.org/jira/browse/DERBY-1651?page=all ] Rick Hillegas updated DERBY-1651: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Moving to 10.2.3.0. Develop a mechanism to migrate mySQL databases to Derby. Migration tool

[jira] Updated: (DERBY-1629) Exceptions thrown by code in procedures or triggers are not handled/thrown correctly by Derby

[ http://issues.apache.org/jira/browse/DERBY-1629?page=all ] Rick Hillegas updated DERBY-1629: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Exceptions thrown by code in procedures or triggers are not handled/thrown

[jira] Updated: (DERBY-1626) TransactionTable.sql fails

[ http://issues.apache.org/jira/browse/DERBY-1626?page=all ] Rick Hillegas updated DERBY-1626: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Moving to 10.2.3.0. TransactionTable.sql fails --

[jira] Updated: (DERBY-1606) derbyrunjartest hangs with wctme5.7 always uses j9_13; hangs with _foundation

[ http://issues.apache.org/jira/browse/DERBY-1606?page=all ] Rick Hillegas updated DERBY-1606: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. derbyrunjartest hangs with wctme5.7 always uses j9_13; hangs with

[jira] Updated: (DERBY-1585) derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet

[ http://issues.apache.org/jira/browse/DERBY-1585?page=all ] Rick Hillegas updated DERBY-1585: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. derbylang/procedureInTrigger: not able to create trigger due to an open

[jira] Updated: (DERBY-1569) analyze 10.1 tests with 10.2 derby to determine which Jira fixes in 10.2 may have existing application impact

[ http://issues.apache.org/jira/browse/DERBY-1569?page=all ] Rick Hillegas updated DERBY-1569: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. analyze 10.1 tests with 10.2 derby to determine which Jira fixes in 10.2

[jira] Updated: (DERBY-1568) run derbyall with low memory configuration for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1568?page=all ] Rick Hillegas updated DERBY-1568: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. run derbyall with low memory configuration for 10.2

[jira] Assigned: (DERBY-1560) When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs

[ http://issues.apache.org/jira/browse/DERBY-1560?page=all ] Rick Hillegas reassigned DERBY-1560: Assignee: (was: Fernanda Pizzorno) Fernanda has moved on to other responsibilities and I do not expect that she will tackle this issue. When

[jira] Updated: (DERBY-1560) When receiving EXTDTA object, the client should avoid keeping the entire LOB in memory for large LOBs

[ http://issues.apache.org/jira/browse/DERBY-1560?page=all ] Rick Hillegas updated DERBY-1560: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. When receiving EXTDTA object, the client should avoid keeping the entire

[jira] Updated: (DERBY-1505) Reference Manual - Limitations of triggered-SQL-statement do not match current behaviour

[ http://issues.apache.org/jira/browse/DERBY-1505?page=all ] Rick Hillegas updated DERBY-1505: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Reference Manual - Limitations of triggered-SQL-statement do not match

[jira] Updated: (DERBY-1482) Update triggers on tables with blob columns stream blobs into memory even when the blobs are not referenced/accessed.

[ http://issues.apache.org/jira/browse/DERBY-1482?page=all ] Rick Hillegas updated DERBY-1482: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Update triggers on tables with blob columns stream blobs into memory even

[jira] Updated: (DERBY-1412) Possible values for derby.storage.rowLocking Derby engine is not currently documented eventhough the property is

[ http://issues.apache.org/jira/browse/DERBY-1412?page=all ] Rick Hillegas updated DERBY-1412: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Possible values for derby.storage.rowLocking Derby engine is not currently

[jira] Updated: (DERBY-1397) Tuning Guide: Puzzling optimizer documentation

[ http://issues.apache.org/jira/browse/DERBY-1397?page=all ] Rick Hillegas updated DERBY-1397: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Tuning Guide: Puzzling optimizer documentation

[jira] Updated: (DERBY-1363) Derby should publish a well defined coding convention per the db project guidlines

[ http://issues.apache.org/jira/browse/DERBY-1363?page=all ] Rick Hillegas updated DERBY-1363: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Derby should publish a well defined coding convention per the db project

[jira] Updated: (DERBY-1343) It is possible to have duplicate entries in conglomerateId of sysconglomerates before DERBY-655 was fixed in 10.0 or 10.1 databases. It is desirable to patch these databas

[ http://issues.apache.org/jira/browse/DERBY-1343?page=all ] Rick Hillegas updated DERBY-1343: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. It is possible to have duplicate entries in conglomerateId of

[jira] Updated: (DERBY-1318) Add an upgrade test to verify that DataSources can be serialized by the previous release and then correctly deserialized by the current release

[ http://issues.apache.org/jira/browse/DERBY-1318?page=all ] Rick Hillegas updated DERBY-1318: - Fix Version/s: 10.3.0.0 (was: 10.2.2.0) Move to 10.3.0.0. Add an upgrade test to verify that DataSources can be serialized by the

[jira] Updated: (DERBY-1316) Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()

[ http://issues.apache.org/jira/browse/DERBY-1316?page=all ] Rick Hillegas updated DERBY-1316: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Wrong value returned by DatabaseMetaData.locatorsUpdateCopy()

[jira] Updated: (DERBY-1312) refreshRow behavior not the same in Derby client and embedded drivers

[ http://issues.apache.org/jira/browse/DERBY-1312?page=all ] Rick Hillegas updated DERBY-1312: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. refreshRow behavior not the same in Derby client and embedded drivers

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

[ http://issues.apache.org/jira/browse/DERBY-1275?page=all ] Rick Hillegas updated DERBY-1275: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Provide a way to enable client tracing without changing the application

[jira] Updated: (DERBY-1273) Sysinfo should print a better message when it gets Security Exceptions accessing classpath info when run under security manager

[ http://issues.apache.org/jira/browse/DERBY-1273?page=all ] Rick Hillegas updated DERBY-1273: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Sysinfo should print a better message when it gets Security Exceptions

[jira] Updated: (DERBY-1256) Remove usage of non-portable methods in derby code

[ http://issues.apache.org/jira/browse/DERBY-1256?page=all ] Rick Hillegas updated DERBY-1256: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Remove usage of non-portable methods in derby code

[jira] Updated: (DERBY-1243) Modify ODBCMetaDataGenerator to use the JDBC4 version of metadata queires as input

[ http://issues.apache.org/jira/browse/DERBY-1243?page=all ] Rick Hillegas updated DERBY-1243: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Modify ODBCMetaDataGenerator to use the JDBC4 version of metadata queires

[jira] Updated: (DERBY-1232) MessageService.getLocalizedMessage(...) should check the validity of its arguments

[ http://issues.apache.org/jira/browse/DERBY-1232?page=all ] Rick Hillegas updated DERBY-1232: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. MessageService.getLocalizedMessage(...) should check the validity of its

[jira] Updated: (DERBY-1209) It would be good to add an example to the SYSCS_UTIL.SYSCS_CHECK_TABLE documentation for how to check all tables

[ http://issues.apache.org/jira/browse/DERBY-1209?page=all ] Rick Hillegas updated DERBY-1209: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. It would be good to add an example to the SYSCS_UTIL.SYSCS_CHECK_TABLE

[jira] Updated: (DERBY-1194) Derby Server and Administration Guide - Managing the Derby Network Server

[ http://issues.apache.org/jira/browse/DERBY-1194?page=all ] Rick Hillegas updated DERBY-1194: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Derby Server and Administration Guide - Managing the Derby Network Server

[jira] Updated: (DERBY-1053) stress.multi test on ibm142 in SANE builds fails with ASSERTION at org.apache.derby.impl.services.cache.CachedItem.unkeep(CachedItem.java:152)

[ http://issues.apache.org/jira/browse/DERBY-1053?page=all ] Rick Hillegas updated DERBY-1053: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. stress.multi test on ibm142 in SANE builds fails with ASSERTION at

Re: Issues marked for fix in 10.2.2 in JIRA

Rick Hillegas wrote: Hi Rajesh, Thanks for bringing up this topic. I have created a new Derby version in JIRA, 10.2.3.0. I think we can reassign most of these issues to 10.2.3.0. Why? Seems like having no fixin might be a better choice, otherwise the same exercise will happen when 10.2.3.0

[jira] Updated: (DERBY-988) jdbcapi/parameterMapping.java fails on Win2003 with 'P3=SQLSTATE(22007): SQL Exception: The syntax of the string representation of a datetime value is incorrect.'

[ http://issues.apache.org/jira/browse/DERBY-988?page=all ] Rick Hillegas updated DERBY-988: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. jdbcapi/parameterMapping.java fails on Win2003 with 'P3=SQLSTATE(22007): SQL

[jira] Updated: (DERBY-980) derbynet/testSecMec.java fails with InterruptedException

[ http://issues.apache.org/jira/browse/DERBY-980?page=all ] Rick Hillegas updated DERBY-980: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. derbynet/testSecMec.java fails with InterruptedException

[jira] Updated: (DERBY-973) Restore fails in OnlineBackupTest1

[ http://issues.apache.org/jira/browse/DERBY-973?page=all ] Rick Hillegas updated DERBY-973: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Restore fails in OnlineBackupTest1 --

[jira] Updated: (DERBY-967) lang/autoincrement.sql intermittently fails on SunOS-5.10_i86

[ http://issues.apache.org/jira/browse/DERBY-967?page=all ] Rick Hillegas updated DERBY-967: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. lang/autoincrement.sql intermittently fails on SunOS-5.10_i86

[jira] Updated: (DERBY-958) Network Client should not print non-ascii token separators in message for NullPointerExceptions or other serious non SQLExceptions

[ http://issues.apache.org/jira/browse/DERBY-958?page=all ] Rick Hillegas updated DERBY-958: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Network Client should not print non-ascii token separators in message for

[jira] Updated: (DERBY-908) YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information on durations.

[ http://issues.apache.org/jira/browse/DERBY-908?page=all ] Rick Hillegas updated DERBY-908: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information

[jira] Updated: (DERBY-857) LDAP user authentication fails under a security manager

[ http://issues.apache.org/jira/browse/DERBY-857?page=all ] Rick Hillegas updated DERBY-857: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. LDAP user authentication fails under a security manager

Re: Should be a statement with error allowed to do a rollback of the active transaction

The key question is whether the statement with error should (or could) rollback the active transaction? Does this same situation arise with an embedded configuration? If so, how does the embedded engine handle your test case? thanks, bryan

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12456093 ] Knut Anders Hatlen commented on DERBY-1471: --- I have looked at patch 3. I don't know enough about layer B streaming to say whether all details of the

Re: Derby Client Driver and LOBs

Hello Tomohito, thank you very much for your reply! Jackrabbit, the JSR-170 reference implementation, uses an embedded derby database to store its content, by default. In order to cluster several repository nodes, derby is started standalone and all cluster nodes, possibly running on different

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (13 issues) Subscriber: derby-dev Key Summary DERBY-1471 Implement layer B streaming for new methods defined in JDBC4.0 http://issues.apache.org/jira/browse/DERBY-1471 DERBY-2146 Translate Getting Started

Regression Test Report - Daily 482709 - Sun DBTG

[Auto-generated mail] *Daily* 482709/2006-12-05 18:00:08 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0517517 096.56% derbyall 064756475 0 155.32%

[jira] Created: (DERBY-2156) message XSDB8 and 42Y32 have references to db2j

message XSDB8 and 42Y32 have references to db2j --- Key: DERBY-2156 URL: http://issues.apache.org/jira/browse/DERBY-2156 Project: Derby Issue Type: Bug Affects Versions: 10.2.1.6, 10.1.3.1

[jira] Commented: (DERBY-2130) Optimizer performance slowdown from 10.1 to 10.2

[ http://issues.apache.org/jira/browse/DERBY-2130?page=comments#action_12456115 ] Bryan Pendleton commented on DERBY-2130: When running against a 10.1 database 10.3 estimates a cost of 1736685, followed up by a cost of 198589 for

Re: Derby Client Driver and LOBs

Dominique Pfister wrote: I looked at the relevant parts of the derby client driver (version 10.1.3.1) and quickly coded a solution for large objects exceeding 1MB, using temporary files that are deleted as soon as the blob is no longer referenced. If there is interest, I could further refine my

Re: Derby Client Driver and LOBs

The client driver fully materializes LOBS when the row is retrieved which would of course explain those errors when the data gets too large. Is this limitation being addressed? Or is there some other way of retrieving binary data from a standalone derby database that bypasses it? DERBY-208

[jira] Updated: (DERBY-813) Clean up coding error in searchClauseTransitiveClosure method in PredicateList.java

[ http://issues.apache.org/jira/browse/DERBY-813?page=all ] Rick Hillegas updated DERBY-813: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Clean up coding error in searchClauseTransitiveClosure method in

[jira] Updated: (DERBY-784) Document predicate push down through union clause in Tuning guide where other similar optimizations are discussed.

[ http://issues.apache.org/jira/browse/DERBY-784?page=all ] Rick Hillegas updated DERBY-784: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Document predicate push down through union clause in Tuning guide where other

[jira] Commented: (DERBY-2146) Translate Getting Started with Derby to Japanese

[ http://issues.apache.org/jira/browse/DERBY-2146?page=comments#action_12456125 ] Laura Stewart commented on DERBY-2146: -- Tomohito - I know of no other updates to the Getting Started Guide for 10.2.2. I assume that you started with the

[jira] Updated: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux

[ http://issues.apache.org/jira/browse/DERBY-700?page=all ] Rick Hillegas updated DERBY-700: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Derby does not prevent dual boot of database from different classloaders on

[jira] Updated: (DERBY-600) Document that DB is booted in read-only mode if not able to create db.lck file

[ http://issues.apache.org/jira/browse/DERBY-600?page=all ] Rick Hillegas updated DERBY-600: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Document that DB is booted in read-only mode if not able to create db.lck

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

[ http://issues.apache.org/jira/browse/DERBY-431?page=all ] Rick Hillegas updated DERBY-431: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Tests needed for verifying proper functioning of

[jira] Updated: (DERBY-425) Developer's guide issues

[ http://issues.apache.org/jira/browse/DERBY-425?page=all ] Rick Hillegas updated DERBY-425: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Developer's guide issues Key:

[jira] Updated: (DERBY-423) Issues for Derby Ref manual

[ http://issues.apache.org/jira/browse/DERBY-423?page=all ] Rick Hillegas updated DERBY-423: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Issues for Derby Ref manual ---

Re: Derby Client Driver and LOBs

Øystein Grøvlen wrote: DERBY-208 is filed to address this. Thanks Øystein ! I linked DERBY-1560 to DERBY-208 because they seem closely related. bryan

[jira] Updated: (DERBY-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password

[ http://issues.apache.org/jira/browse/DERBY-391?page=all ] Rick Hillegas updated DERBY-391: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Tools and Utilities guide does not document ij.datasource, ij.user, nor

[jira] Updated: (DERBY-338) Move checks for referential constraints from DDL execution time to DML execution time

[ http://issues.apache.org/jira/browse/DERBY-338?page=all ] Rick Hillegas updated DERBY-338: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. Move checks for referential constraints from DDL execution time to DML

[jira] Updated: (DERBY-289) Enable code sharing between Derby client and engine

[ http://issues.apache.org/jira/browse/DERBY-289?page=all ] Rick Hillegas updated DERBY-289: Fix Version/s: 10.3.0.0 (was: 10.2.2.0) Move to 10.2.3.0. Enable code sharing between Derby client and engine

[jira] Updated: (DERBY-289) Enable code sharing between Derby client and engine

[ http://issues.apache.org/jira/browse/DERBY-289?page=all ] Rick Hillegas updated DERBY-289: Er, make that 10.3.0.0. Enable code sharing between Derby client and engine --- Key: DERBY-289

[jira] Updated: (DERBY-281) TestHarness should read bootPassword as a property

[ http://issues.apache.org/jira/browse/DERBY-281?page=all ] Rick Hillegas updated DERBY-281: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. TestHarness should read bootPassword as a property

  1   2   >