Author: arminw
Date: Sat Jan 28 03:35:49 2006
New Revision: 373143
URL: http://svn.apache.org/viewcvs?rev=373143&view=rev
Log:
update
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=373143&r1=373142&r2=373143&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 28 03:35:49 2006
@@ -20,14 +20,16 @@
NEW FEATURES:
- Better support for attributes containing expressions ie. sum(0.9 * price *
stock).
Restriction: All attributes contained in the expressions have to belong to
the same table !
-
+- Add new CGLib based PersistentField implementation. It requires JavaBeans
compliant
+ getter/setter. It's three times faster than the direct field access via
reflection.
NOTES:
+- OJB.properties file changed, replace it when update.
- Documentation update and improvement: section about using RowReader and
using a
specific RowReader on class level.
CHANGES:
--
+- ODMG-api implementation, internal used locking interface changed to improve
performance.
BUG FIXES:
Please refer to our Bug tracking site
(https://issues.apache.org/jira/browse/OJB)
@@ -38,8 +40,9 @@
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.
+ needs insert. This will be configurable in next upcoming major 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
