[jira] Resolved: (DERBY-2143) Updated localized messages for Derby 10.2

[ http://issues.apache.org/jira/browse/DERBY-2143?page=all ] Andrew McIntyre resolved DERBY-2143. Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed to 10.2 branch with revision 483352 and merged

[jira] Updated: (DERBY-2143) Updated localized messages for Derby 10.2

[ http://issues.apache.org/jira/browse/DERBY-2143?page=all ] Andrew McIntyre updated DERBY-2143: --- Attachment: derby-2143-v2.diff Thank you very much, Myrna, for identifying the descrepencies between the old and new Brazilian Portuguese messages. I've

[jira] Commented: (DERBY-538) Investigate using the standard java.net.URLClassLoader for database class loading.

[ http://issues.apache.org/jira/browse/DERBY-538?page=comments#action_12456267 ] Daniel John Debrunner commented on DERBY-538: - Java bug 4950148 means that the closing of the jar file opened by URClassLoader is delayed until that obj

Re: javadoc warnings due to r 482426?

Myrna van Lunteren wrote: Hi, I am seeing some javadoc warnings, r482426 looks the last one to have changed EmbedDatabaseMetaData and SystemProcedures. Fixed, an @see tag cannot refer to an http URL directly, it needs to be like: @see href="http://mathworld.wolfram.com/HyperbolicFunctions.

javadoc warnings due to r 482426?

Hi, I am seeing some javadoc warnings, r482426 looks the last one to have changed EmbedDatabaseMetaData and SystemProcedures. Anyone else seeing this? Thx, Myrna javadoc] [snippedpath]\java\engine\org\apache\derby\impl\jdbc\EmbedDatabaseMetaData.java:90: warning - Tag @see:illegal character:

[jira] Commented: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables

[ http://issues.apache.org/jira/browse/DERBY-606?page=comments#action_12456260 ] Suresh Thalamati commented on DERBY-606: derby606_impl-v5.diff : This patch looks good to be committed. Did you run the regression tests ? For some reason I

[jira] Commented: (DERBY-2153) suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory

[ http://issues.apache.org/jira/browse/DERBY-2153?page=comments#action_12456257 ] Daniel John Debrunner commented on DERBY-2153: -- Patch enables me to run the junit tests under J2ME/CDC/Foundation again. > suites.All falls over with

[jira] Created: (DERBY-2160) Network Servlet needs adjustment to implement point 3.2.2 of the wcag 2.0 accessibility guidelines

Network Servlet needs adjustment to implement point 3.2.2 of the wcag 2.0 accessibility guidelines -- Key: DERBY-2160 URL: http://issues.apache.org/jira/browse/DERBY-2

[jira] Updated: (DERBY-2153) suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory

[ http://issues.apache.org/jira/browse/DERBY-2153?page=all ] A B updated DERBY-2153: --- Attachment: d2153_v1.patch Attaching a patch, d2153_v1.patch, to create a new file, junit/JAXPFinder.java, that is only instantiated when all required XML classes are in the cla

[jira] Commented: (DERBY-2159) The Network Server Servlet needs to use html lang= for web content accessibility guidelines 2.0

[ http://issues.apache.org/jira/browse/DERBY-2159?page=comments#action_12456244 ] Myrna van Lunteren commented on DERBY-2159: --- So, the resulting would be something like this in html: > The Network Server Servlet needs to use html lan

[jira] Created: (DERBY-2159) The Network Server Servlet needs to use html lang= for web content accessibility guidelines 2.0

The Network Server Servlet needs to use html lang= for web content accessibility guidelines 2.0 --- Key: DERBY-2159 URL: http://issues.apache.org/jira/browse/DERBY-2159

[jira] Updated: (DERBY-1746) upgrade tests should start using 10.1.3 released builds

[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ] Myrna van Lunteren updated DERBY-1746: -- Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Affects Version/s: 10.2.1.6 (was: 10.2.3.0) >

[jira] Updated: (DERBY-1746) upgrade tests should start using 10.1.3 released builds

[ http://issues.apache.org/jira/browse/DERBY-1746?page=all ] Myrna van Lunteren updated DERBY-1746: -- Affects Version/s: 10.2.3.0 (was: 10.2.1.6) I've not had any ideas to fix the problem with the 10.1.3. jars. > upgrade

[jira] Updated: (DERBY-1760) remote server testing with 10.2 snapshot showed 8 failures

[ http://issues.apache.org/jira/browse/DERBY-1760?page=all ] Myrna van Lunteren updated DERBY-1760: -- Fix Version/s: (was: 10.2.2.0) Changing this to unknown. It's not something that should stop release of any 10.2 version. What gets fixed thou

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

Bryan Pendleton wrote: 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? Some exceptions are transaction level, such

Re: Issues marked for fix in 10.2.2 in JIRA

Daniel John Debrunner wrote: 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 exer

[jira] Created: (DERBY-2158) test lang.UpdatableResultSetTest.testUpdateXXXWithAllDatatypes fails with wctme5.7 (j9) foundation

test lang.UpdatableResultSetTest.testUpdateXXXWithAllDatatypes fails with wctme5.7 (j9) foundation -- Key: DERBY-2158 URL: http://issues.apache.org/jira/browse/DERBY-2

[jira] Updated: (DERBY-2157) SqlExceptionTest.testChainedException and .testNextException fail with wctme5.7 foundation

[ http://issues.apache.org/jira/browse/DERBY-2157?page=all ] Myrna van Lunteren updated DERBY-2157: -- Summary: SqlExceptionTest.testChainedException and .testNextException fail with wctme5.7 foundation (was: SqlException) Issue

[jira] Created: (DERBY-2157) SqlException

SqlException Key: DERBY-2157 URL: http://issues.apache.org/jira/browse/DERBY-2157 Project: Derby Issue Type: Bug Reporter: Myrna van Lunteren -- This message is automatically generated by JIRA. - If you think it

[jira] Commented: (DERBY-2153) suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory

[ http://issues.apache.org/jira/browse/DERBY-2153?page=comments#action_12456171 ] A B commented on DERBY-2153: > I think that could be simplified with: >DocumentBuilderFactory.newInstance().getClass() Yes, you're absolutely right. I'll include

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

Merging Getting Started and Working with Derby is a GREAT idea, Laura. Currently WWD is much more about getting started than Getting Started is. If I can help with this, please let me know! It would be good to do it for 10.3. Kim Laura Stewart (JIRA) wrote: [ http://issues.apache.org/jira

Re: Re: Re: build error ?

On 12/6/06, Mamta Satoor <[EMAIL PROTECTED]> wrote: 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. Maybe the real co

[jira] Commented: (DERBY-2153) suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory

[ http://issues.apache.org/jira/browse/DERBY-2153?page=comments#action_12456159 ] Daniel John Debrunner commented on DERBY-2153: -- Just to be clear Derby is supoorted on J2ME/CDC/Foundation 1.0 with JSR 169. J2ME/CDC/Foundation 1.0 is

[jira] Commented: (DERBY-1972) Working With Derby needs some formatting fixes and other minor cleanup

[ http://issues.apache.org/jira/browse/DERBY-1972?page=comments#action_12456158 ] Kim Haase commented on DERBY-1972: -- Thanks, Laura! I'm glad we are in agreement about what doc conventions are normal. I agree with proposing to the list that we

[jira] Commented: (DERBY-2153) suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory

[ http://issues.apache.org/jira/browse/DERBY-2153?page=comments#action_12456156 ] Daniel John Debrunner commented on DERBY-2153: -- The code that uses DocumentBuilderFactory in junit.XML has this Class.forName(DocumentBuilderFactory.n

[jira] Updated: (DERBY-2083) Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.

[ http://issues.apache.org/jira/browse/DERBY-2083?page=all ] Daniel John Debrunner updated DERBY-2083: - Derby Info: [Patch Available] Running tests on patch, don't expect any failures since (at the moment) it's just adding calls that do nothing.

[jira] Updated: (DERBY-2083) Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.

[ http://issues.apache.org/jira/browse/DERBY-2083?page=all ] Daniel John Debrunner updated DERBY-2083: - Attachment: d2083_store_shutdown_diff.txt Patch so that the store calls shutdown() on its StorageFactory. Is only a partial solution as the s

[jira] Updated: (DERBY-1102) Test triggerGeneral (at least) uses internal old api's related to triggers.

[ http://issues.apache.org/jira/browse/DERBY-1102?page=all ] Daniel John Debrunner updated DERBY-1102: - Fix Version/s: 10.3.0.0 (was: 10.2.2.0) no plans to fix in 10.2.2 > Test triggerGeneral (at least) uses internal old a

[jira] Updated: (DERBY-927) Cleanup code in the monitor to clarify the relationship between StorageFactory and PersistentService

[ http://issues.apache.org/jira/browse/DERBY-927?page=all ] Daniel John Debrunner updated DERBY-927: Fix Version/s: 10.3.0.0 (was: 10.2.2.0) Not planning on fixing this for 10.2.2 > Cleanup code in the monitor to clarify t

Re: Derby Client Driver and LOBs

Øystein Grøvlen wrote: 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 i

Re: Issues marked for fix in 10.2.2 in JIRA

My apologies for the recent JIRA noise: I have moved the unassigned 10.2.2 issues to 10.2.3. That leaves us with 19 10.2.2 issues which are currently assigned. It would be very helpful if the assignees could take a look at these issues (just use Rajesh's filter link below). The assignees are in

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 ref

[jira] Updated: (DERBY-1782) When a privilege is revoked at table level, Derby should only drop objects that require that particular privilege and not all the objects that require some form of privile

[ http://issues.apache.org/jira/browse/DERBY-1782?page=all ] Rick Hillegas updated DERBY-1782: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > When a privilege is revoked at table level, Derby should only drop objects

[jira] Updated: (DERBY-1928) Update table "Support for SQL-92 Features: Basic schema manipulation" for GRANT/REVOKE

[ http://issues.apache.org/jira/browse/DERBY-1928?page=all ] Rick Hillegas updated DERBY-1928: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > Update table "Support for SQL-92 Features: Basic schema manipulation" for

[jira] Updated: (DERBY-2053) Dev Guide: Syntax errors in SQL tips -> Tricks of the VALUES clause -> Multiple rows

[ http://issues.apache.org/jira/browse/DERBY-2053?page=all ] Rick Hillegas updated DERBY-2053: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > Dev Guide: Syntax errors in SQL tips -> Tricks of the VALUES clause -> >

[jira] Updated: (DERBY-1935) Reference Manual - Derby Limitations

[ http://issues.apache.org/jira/browse/DERBY-1935?page=all ] Rick Hillegas updated DERBY-1935: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > Reference Manual - Derby Limitations > ---

[jira] Updated: (DERBY-2128) The wrod class appears twice for the message SIF01.V

[ http://issues.apache.org/jira/browse/DERBY-2128?page=all ] Rick Hillegas updated DERBY-2128: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > The wrod class appears twice for the message SIF01.V > ---

[jira] Updated: (DERBY-2132) EmbeddedDriver should include JDBC 4.0 in the list of versions it supports in its javadoc

[ http://issues.apache.org/jira/browse/DERBY-2132?page=all ] Rick Hillegas updated DERBY-2132: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > EmbeddedDriver should include JDBC 4.0 in the list of versions it supports

[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 ] Rick Hillegas updated DERBY-264: Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > This enhancement to allow expressions in ORDER BY clause will require > docu

[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 >

[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-2

[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-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 > exe

[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 > ij

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-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 > --- > >

[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-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 > ClientBaseDataSource.setC

[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 fil

[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] 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 1

[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] 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 > Predicate

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-20

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

[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

[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

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% org.apache.derbyTesting.

[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 wit

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 ma

[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 imple

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] 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 > ---

[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-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-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-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-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-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

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-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 > org

[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-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-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-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-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-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-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-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-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-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-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 > sysconglo

[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-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-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-1460) Instability in storerecovery suite when run against jar files on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-1460?page=all ] Rick Hillegas updated DERBY-1460: - Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > Instability in storerecovery suite when run against jar files on jdk1.6 >

[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-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-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 L

[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 rec

[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] 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-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-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 > _fo

[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-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-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-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-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 >

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: Th

  1   2   >