You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ar...@apache.org on 2005/12/12 18:29:11 UTC
cvs commit: db-ojb release-notes.txt
arminw 2005/12/12 09:29:11
Modified: . Tag: OJB_1_0_RELEASE release-notes.txt
Log:
update release notes
Revision Changes Path
No revision
No revision
1.54.2.53 +25 -6 db-ojb/release-notes.txt
Index: release-notes.txt
===================================================================
RCS file: /home/cvs/db-ojb/release-notes.txt,v
retrieving revision 1.54.2.52
retrieving revision 1.54.2.53
diff -u -r1.54.2.52 -r1.54.2.53
--- release-notes.txt 6 Oct 2005 22:14:00 -0000 1.54.2.52
+++ release-notes.txt 12 Dec 2005 17:29:11 -0000 1.54.2.53
@@ -28,11 +28,9 @@
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
- as global property in class ImplementationExt and for a specific transaction in
- class TransactionExt:
+ 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
- - 'noteUserOrder' If true the order of persisting/locking method calls
- determine the order of objects before 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
@@ -83,7 +81,28 @@
* 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org