arminw 2005/01/12 03:52:28
Modified: . Tag: OJB_1_0_RELEASE release-notes.txt
Log:
update notes
Revision Changes Path
No revision
No revision
1.54.2.21 +10 -1 db-ojb/release-notes.txt
Index: release-notes.txt
===================================================================
RCS file: /home/cvs/db-ojb/release-notes.txt,v
retrieving revision 1.54.2.20
retrieving revision 1.54.2.21
diff -u -r1.54.2.20 -r1.54.2.21
--- release-notes.txt 27 Nov 2004 23:47:18 -0000 1.54.2.20
+++ release-notes.txt 12 Jan 2005 11:52:28 -0000 1.54.2.21
@@ -41,6 +41,11 @@
- Use of database identity column (SequenceManagerNativeImpl). Move assign
of PK values from
PersistenceBrokerImpl to JdbcAccessImpl#executeInsert. Remove usage of
SequenceManager#setReferenceFKs,
will be handled by OJB in same way as without usage of database identity
column.
+- Method signature changes in
+ org.apache.ojb.broker.locking.LockMap#removeWriter/Reader. Take care when
using own
+ LockMap implementations.
+- odmg-api: Introduced new object reodering implementation (replaces old
algorithm
+ in ObjectEnvelopeTable).
BUG FIXES:
Please refer to our Bug tracking site
(http://issues.apache.org/scarab/servlet/scarab/)
@@ -49,6 +54,10 @@
- Managed Environment: Fix problem of abandoned connections and statements
(e.g. detected
by JBoss) when query (iterator) result sets only partially materialized.
+- Fix bug in ObjectCacheDefaultImpl resolve cache object conflicts, see
+ http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=15063
+- LockManager#releaseLock, when a write lock was found all read locks will
be released too.
+ http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=14885
- Fix problem with automatic generated sequence names in
SequenceManagerHighLowImpl and
SequenceManagerInMemoryImpl when different DB use the same table and
column name for auto
incremented fields.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
