Author: arminw
Date: Sat Jan 21 09:38:42 2006
New Revision: 371092
URL: http://svn.apache.org/viewcvs?rev=371092&view=rev
Log:
update notes
Modified:
db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt
Modified: db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt
URL:
http://svn.apache.org/viewcvs/db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt?rev=371092&r1=371091&r2=371092&view=diff
==============================================================================
--- db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt (original)
+++ db/ojb/branches/OJB_1_0_RELEASE/release-notes.txt Sat Jan 21 09:38:42 2006
@@ -15,6 +15,43 @@
---------------------------------------------------------------------
+Release 1.0.5
+---------------------------------------------------------------------
+NEW FEATURES:
+
+
+NOTES:
+- Documentation update and improvement: section about using RowReader and
using a
+ specific RowReader on class level.
+
+CHANGES:
+-
+
+BUG FIXES:
+Please refer to our Bug tracking site
(https://issues.apache.org/jira/browse/OJB)
+to see details for a bug with id OJB-xxx.
+
+-
+
+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.
+
+
+---------------------------------------------------------------------
Release 1.0.4
---------------------------------------------------------------------
NEW FEATURES:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
