Apache Derby is a subproject of the Apache DB project. Derby is a pure Java relational database engine which conforms to the ISO/ANSI SQL and JDBC standards. Derby aims to be easy for developers and end-users to work with.

IMPORTANT NOTICE:

If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid any chance of database corruption due to an issue with multiple threads accessing a database that is documented in DERBY-3347.

This bug can cause unrecoverable database corruption during periods of heavy, multi-thread I/O operations. The error produced in the test case used to diagnose the problem was:

ERROR XSDB3: Container information cannot change once written: was 0, now 80.

It is felt that other errors might also be generated when this type of corruption occurs. The corruption message will most likely refer to page 0 of the container. For example:

ERROR XSDG1: Page Page(0 ,Container(0, 5856)) could not be written...

This bug corrupts the pages on disk and can go unnoticed. If you do not run database consistency checks regularly it is recommended you begin doing so as soon as possible after the upgrade. To insure that corruption has not already occurred in existing databases, after upgrade run the database consistency check at least once to validate all tables in the database. This proalso check that the previous backup did not also have the corruption.

In some cases one may recover data from the existing database, depending on the extent of the corruption, but will require by hand data recovery. Depending on the type of corruption this may be successful or not. one should consult the Derby list if attempting this recovery - no automatic software solution to this recovery exists.

Version 10.3.3.0 can be downloaded from: http://db.apache.org/derby/releases/release-10.3.3.0.cgi

Version 10.4.1.3 can be downloaded from: http://db.apache.org/derby/releases/release-10.4.1.3.cgi

For help or questions: http://db.apache.org/derby/derby_mail.html

----

-- The Apache Derby Project

]]> [ Category : Apache DB ]

Apache Derby is a subproject of the Apache DB project. Derby is a pure Java relational database engine which conforms to the ANSI SQL and JDBC standards. Derby aims to be easy for developers and end-users to work with.

Derby 10.3.2.1 can be obtained from the Derby download site:

http://db.apache.org/derby/derby_downloads.html

Derby 10.3.2.1 contains many bug fixes for issues present in earlier releases, including important fixes for territory based collation.

Please try 10.3.2.1.

----

-- The Apache Derby Project

]]> [ Category : Apache DB ]

Apache Derby is a subproject of the Apache DB project. Derby is a pure Java relational database engine which conforms to the ANSI SQL and JDBC standards. Derby aims to be easy for developers and end-users to work with.

Derby 10.3.1.4 can be obtained from the Derby download site:

http://db.apache.org/derby/derby_downloads.html

Derby 10.3.1.4 introduces the following new capabilities:

• Security
  • Restricts shutdown, encryption, and upgrade powers to the DBA.
  • Installs a default security manager for the Network Server.
  • Supports SSL encryption of Network Server traffic.
• SQL
  • Supports the dropping and renaming of columns.
  • Creates empty tables from queries.
  • Makes some CREATE TRIGGER clauses optional.
  • Adds ANSI TRIM capabilities.
• JDBC
  • Supports all JDBC methods on BLOBs and CLOBs.
  • Expands embedded support for autogenerated keys.
• Performance and Memory Usage
  • Reduces CPU usage in embedded mode.
  • Improves IN list processing.
  • Introduces LOB locators for network clients.
• Administration
  • Supports databases with language-specific ordering of character data.
  • Allows import/export of LOBs.
  • Enables client-side tracing without changing the application.
  • Supports XAResource.setTransactionTimeout.
  • Adds system procedure support for setting a user's connection level authorization.
  • Adds a system procedure to empty the statement cache.
  • Supports diagnostic VTIs with parameters.
• Platforms and Testing
  • Supports J2ME/CDC/Foundation 1.1.
  • Removes support for JDK 1.3 and J2ME/CDC/Foundation 1.0.
  • Converts many tests to JUnit's assertion-based framework.

----

-- The Apache Derby project

]]> [ Category : Apache DB ]

Derby is a pure Java, standards-based relational database engine. Derby aims to be an easy to use solution for data management for software developers with zero administration for end users.

Derby 10.1.3.1 can be downloaded at:

http://db.apache.org/derby/releases/release-10.1.3.1.cgi

What's new in 10.1.3.1:

• Critical fixes for network client when used with a transaction manager (XA)
• A critical data integrity fix when running with IBM J2RE 1.5.0 SR2.
• fixes for network client when used with a transaction manager (XA)
• Improved Network Server stability and reliability
• Improved memory usage for the Network Client
• Improved query performance for UNION queries and subqueries
• Better handling of text encoding on systems with non-ASCII native encoding
• More reliable behavior of scrollable insensitive result sets
• Updated documentation
• A new distribution that includes line number information, lib-debug, has been added to assist in filing and tracking down Derby issues
• Many important fixes to correct issues with data integrity, correct memory leaks and address other product defects

A complete list of fixes is available on the download page.

----

-- The Apache Derby Project

]]> [ Category : Apache DB ]

The Apache OJB team is happy to announce the 1.0.4 release:

---------------------------------------------------------------------
Release 1.0.4
---------------------------------------------------------------------

NEW FEATURES:

• Support for embedded & network Derby (only distinct count queries don't work yet)
• Added ability to prepare the database for OJB's unit tests via DdlUtils (instead of Torque) Note that this is required when running the tests against Derby
• [OJB-10] - Configurable Proxy generation (including CGLIB based generation)
• [OJB-31] - Configurable JDBC driver-setting setFetchSize
• [OJB-14] - Setting custom JDBC driver tuning options trough jdbc-connection-descriptor
• [OJB-6] - Support for stored procedures returning ResultSet.
• [OJB-41] - ODMG-api: Allow cascading delete using auto-delete setting in metadata
• [OJB-66] - Allow to specify a sequence start element for SequenceManagerNextValImpl. Fixed for Oracle, PostgreSQL, MaxDB/SapDB, DB2. Additionally sequence properties like 'increment by', 'cache', 'order',... are supported too. See 'sequence manger' guide and javadoc
• Add new ODMG extensions and configuration properties. All properties can be set at runtime as global property in class ImplementationExt and for a specific transaction in class TransactionExt:
  • 'ordering' Allow to dis-/enable OJB's object ordering on transaction commit
  • 'implicitLocking' Dis-/enable OJB's implicit locking
• Add new property 'TxCheck' in OJB.properties file. When enabled, on PB store and delete calls OJB checks for a running PB-tx, if not found an error is logged in order to avoid store/delete calls without a running PB-tx (while development).

NOTES:

• Internal OJB class configuration files are changed, don't forget to replace these files on upgrade from older version (by default the internal used classes are located in repository_internal.xml).
• Improved performance comparison tests ('ant perf-test' and 'ant performance'). Now the tests more fair for registered API's
• In order to facilitate [OJB-10] the constructor signature of VirtualProxy has been changed.

CHANGES:

• INTERNAL API CHANGES: Pluggable class interfaces changed to support and fix OJB-31, OJB-6, OJB-63:
  • StatementsForClassIF
  • StatementManagerIF
  • Platform
  • RowReader
  • SqlGenerator
• Configurable ProxyFactory is now available. Both JDK-based (default) and CGLIB are provided. CGLIB-based generation allows for proxies to be generated for all persistent classes, and not just ones that implement an interface.
• Change in behavior of property 'useAutoCommit="1"' in jdbc-connection-descriptor detailed info can be found in reference guide of the repository file
• ConnectionFactoryManagedImpl is declared deprecated. Now OJB automatic detect the running JTA-transaction and suppress critical method calls on the used connection
• Removed deprecated SequenceManager implementation SequenceManagerMySQLImpl
• Remove unused method #setReferenceFKs from SequenceManager interface
• ODMG-api: Method behavior of ImplementationImpl#setImplicitLocking(boolean) changed. Now this method set the global property for 'implicitLocking'. Old version only changed the implicit locking behavior for the current used transaction, this is moved to TransactionExt#setImplicitLocking
• Internal used OJB_HL_SEQ table changed. Remove of deprecated column. If the SequenceManagerHighLowImpl was used and problems occur after upgrade, please drop and recreate this table without removed column
• Cleanup naming of 'PersistentField' implementation classes: Remove deprecated classes, rename implementation classes, declare all ...ImplNew classes as deprecated. See OJB.properties file.
• Upgraded ANTLR to v2.7.5 (OQL and JDOQL parser classes have been re-generated)
• Upgraded commons-dbcp to v1.2.1
• Upgraded commons-pool to v1.2
• Upgraded commons-beanutils to v1.7
• Upgraded commons-logging to v1.0.4
• Upgraded commons-collections to v3.1
• Upgraded hsql to v1.8.0.2
• Upgraded Torque to v3.1.1

BUG FIXES:

• [OJB-18] - ODMG ordering problem with circular/bidirectional 1:1 references
• [OJB-25] - Inheritance (each subclass on separate table) PK problem with nextval SequenceManager
• [OJB-26] - JDBC-ODBC bridge problem
• [OJB-27] - [ODMG] Foreign key violation
• [OJB-29] - Infinite loop in case of refresh=true and cycles in references
• [OJB-40] - CallableStatement check doesn't work with maxDB
• [OJB-42] - MsSQLServer, auto-generated querry error (m:n relation)
• [OJB-44] - ReferenceMap$Entry keeps growing over period of application usage.
• [OJB-52] - KeyConstraintViolatedException during store
• [OJB-54] - ConnectionFactoryManagedImpl may try to use pool
• [OJB-55] - Getting foreignkeyField's FieldDescriptor is failing if the foreignkey field is defined in the base class
• [OJB-59] - Incorrect identity management in SequenceManagerNativeImpl because of wrong plate-forme settings
• [OJB-62] - addPathClass in QueryByCriteria does not consider inheritance
• [OJB-63] - Bug when query against objects mapped on multiple joined tables ("super"-references)
• [OJB-70] - Connection reset by peer: socket write error
• [OJB-76] - OJB MtoN implementor failes to work properly with composite M&N keys that have some fields common.
• [OJB-77] - PlatformMsSQLServerImpl.getLastInsertIdentityQuery creates incorrect SQL statement to pull the identity from the last

KNOWN ISSUES:

• Auto-Detection for insert/update objects checks to avoid DB queries the PK fields of the object. If at least one PK field is 'NULL' or if primitive field '0', OJB assume the object is new and needs insert. This will be configurable in next upcoming version. Workaround for PB-api: use method PB#store(Object obj, ObjectModification mod) to state update or insert.
• Batch handling doesn't work properly with optimistic locking. This will be fixed in version 1.1
• Subqueries are not extent aware. see QueryTest#testSubQueryAgainstExtents
• Managed Environment: When run OJB in managed environment and using PBStateListener, the call of PBStateListener#beforeClose(PBStateEvent event) is made twice when a PB instance was closed in a JTA-tx (for the first time when PB.close() was called in bean on the PB handle, second time when the JTA-tx completes)
• otm-api: The OTM API has a known caching issue and should not be considered for code used in production environments. The future of the OTM layer will be subject for discussion on the OJB developers list, if you are using it - please subscribe to ojb-dev and make your voice heard.
• Oracle9i platform: when using statement batching, there is a 2k limit on BLOB + 4k limit on CLOB.

----

-- The Apache OJB team

]]> [ Category : Apache DB ]

http://db.apache.org/derby/

Apache Derby 10.1.1.0 can be downloaded from the following page:

http://db.apache.org/derby/releases/release-10.1.1.0.cgi

Apache Derby is a pure Java, standards-based relational database engine. Derby aims to be an easy to use solution for data management for software developers with zero administration for end users.

This release includes a new open source network client driver, as well as a number of other new features and enhancements:

• Support for J2ME/CDC/Foundation with JSR-169 JDBC subset
• Online compress functionality for reclaiming disk space during operation
• XA support for Network Server
• Increased identifier lengths to 128 characters for all identifiers
• Added SQL: INTERSECT and EXCEPT
• Added SQL: SYNONYM
• JDBC Updatable Result Sets
• ORDER by expressions
• Allow insertions into an identity column
• Support for explicit Java method signature in function and procedure definitions

See the CHANGES file in the distributions for a full list of other changes.

----

-- The Apache Derby Project

]]> [ Category : Apache DB ]

Downloads:

http://www.apache.org/dyn/closer.cgi/db/ojb/db-ojb-1.0.3/

]]> [ Category : Apache DB ]

Downloads:

http://www.apache.org/dyn/closer.cgi/db/ojb/db-ojb-1.0.2/

]]> [ Category : Apache DB ]

Our primary vision is to build an enterprise directory server platform (Apache Directory Server) and its components where other Internet services snap in to store their data within the directory so they may be managed using LDAP. Those services include LDAP itself, DNS, DHCP, SLP, UDDI, NTP, and most importantly Kerberos, which can integrate with the services to provide full-featured network authentication service.

Features of Apache Directory Server:

• Designed as an LDAP and X.500 experimentation platform.
• The server exposes all aspects of administration via a special system backend.
• Both the backend subsystem and the frontend are separable and independently embeddable.
• Provides a server side JNDI LDAP provider which directly interacts with the backend storage.
• Powered by MINA, a powerful framework for building Internet protocol servers.

Coming soon:

• Remote management via JMX.
• Java-based triggers and stored procedures.

The Apache Directory team is looking for developers and users to work with the server and give feedback. Mailing list information is at: http://directory.apache.org/mailing-lists.html

Check the Apache Directory project at: http://directory.apache.org/

The Apache Software Foundation provides organizational, legal, and financial support for a broad range of open source software projects. The Foundation provides an established framework for intellectual property and financial contributions that simultaneously limits contributors potential legal exposure. Through a collaborative and meritocratic development process, Apache projects deliver enterprise-grade, freely available software products that attract large communities of users.

----

-- The Apache Directory Team

]]> [ Category : Apache DB ]
[ Category : Apache Directory ]
[ Category : Apache Incubator ]
[ Category : Apache Software Foundation ]

Our primary vision is to build an enterprise directory server platform and its components where other Internet services snap in to store their data within the directory so they may be managed using LDAP. Those services include LDAP itself, DNS, DHCP, SLP, UDDI, NTP, and most importantly Kerberos, which can integrate with the services to provide full-featured network authentication service.

Features:

• Designed as an LDAP and X.500 experimentation platform.
• The server exposes all aspects of administration via a special system backend.
• Both the backend subsystem and the frontend are separable and independently embeddable.
• Provides a server side JNDI LDAP provider which directly interacts with the backend storage.
• Powered by Staged Event Driven Architecture (SEDA) which can handle large amounts of concurrency.

Coming soon:

• Remote management via JMX.
• Java-based triggers and stored procedures.

The Apache Directory team is looking for developers and users to work with the server and give feedback. Mailing list information is at: http://incubator.apache.org/directory/mailing-lists.html

Please note that the Directory Project is an effort undergoing incubation at the Apache Software Foundation (ASF). While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

Check ApacheDS at: http://incubator.apache.org/directory/

The Apache Software Foundation provides organizational, legal, and financial support for a broad range of open source software projects. The Foundation provides an established framework for intellectual property and financial contributions that simultaneously limits contributors potential legal exposure. Through a collaborative and meritocratic development process, Apache projects deliver enterprise-grade, freely available software products that attract large communities of users.

----

-- The Apache Directory Team

]]> [ Category : Apache DB ]
[ Category : Apache Incubator ]

Derby is a pure Java, standards-based relational database engine. Derby aims to be an easy to use solution for data management for software developers with zero administration for end users.

The release serves as a baseline for future development of Derby, and to allow users to begin using an official release. It also contains a number of bug fixes and other changes. See the CHANGES file in the distribution for a full list of changes.

Apache Derby is an effort undergoing incubation at the Apache Software Foundation (ASF). Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision-making process have stabilised in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

----

-- The Apache Derby Development Community (in Apache Incubator Project)

]]> [ Category : Apache DB ]
[ Category : Apache Incubator ]

Main new feature of this version is the first official release of the maven-torque-plugin which allows Java and SQL source code creation with Torque through integration with Apache Maven.

The release is primarily available through our download page at http://db.apache.org/torque-31/download.html

Apache Mirror System
====================

http://www.apache.org/dyn/closer.cgi/db/torque/torque-3.1.1

or

http://www.apache.org/dist/db/torque/torque-3.1.1 (until the mirrors are synchronized)

Maven repository
================

http://www.ibiblio.org/maven/torque/
http://www.apache.org/dist/java-repository/torque/

---------------------------------------------------------------------

-- The Apache DB/Torque Team

]]> [ Category : Apache DB ]

Full release notes: http://db.apache.org/ojb/release-notes.txt

Downloads: (mirrors)
http://www.apache.org/dyn/closer.cgi/db/ojb/db-ojb-1.0.1/

----

-- Apache DB/OJB Team

]]> [ Category : Apache DB ]

http://db.apache.org/builds/ojb/1.0.0/

Apache Db/OJB Project Team

]]> [ Category : Apache DB ]