db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From arm...@apache.org
Subject cvs commit: db-ojb release-notes.txt
Date Sat, 11 Sep 2004 12:44:55 GMT
arminw      2004/09/11 05:44:55

  Modified:    .        Tag: OJB_1_0_RELEASE release-notes.txt
  add notes for 1.0.2
  Revision  Changes    Path
  No                   revision
  No                   revision  +54 -1     db-ojb/release-notes.txt
  Index: release-notes.txt
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision
  retrieving revision
  diff -u -r1.54.2.7 -r1.54.2.8
  --- release-notes.txt	8 Sep 2004 20:06:38 -0000
  +++ release-notes.txt	11 Sep 2004 12:44:55 -0000
  @@ -8,6 +8,59 @@
   relational databases. OJB provides ODMG and JDO interfaces.
  +Release 1.0.2
  +- !!!In managed enviroments the org.odmg.Transaction#abort() call no longer throws an
  +TransactionAbortedExceptionOJB, instead OJB does internal cleanup and set used
  +JTA-tx to setRollbackOnly if possible. Thus the client does no longer get an RemoteException.
  +The user have to throw an EJBException by himself to notify the client.
  +Please refer to our Bug tracking site (http://issues.apache.org/scarab/servlet/scarab/)
  +under http://issues.apache.org/scarab/servlet/scarab/issues/id/OJBxxx
  +to see details for a bug with id OJBxxx.
  +- Fix bug in SequenceManagerNativeImpl used to support DB identity columns, make counter
  +temporary keys static to prevent lock not granted exceptions on insert of new objects.
  +- odmg-api: In managed environment odmg-api does clenup internal stuff (cache, locking)
  +Synchronization#afterCompletion(int status) was called by the JTA-TxManager instead doing
all this
  +stuff in #beforeCompletion()
  +- odmg-api: Assign FK for 1:1 relations when persistent objects are written to DB, instead
when objects
  +were locked.
  +- odmg-api: If a user exchange already existing objects in 1:n references without changing
the size
  +  of the collection, the main object will not become dirty and the FK values of the exchanged
  +  will not be updated.
  +  E.g. two objects obj_1 anf obj_2 with 1:n reference to ref objects, each with one
  +  existing/persistent reference object, obj_1{ref_1} and obj_2{ref_2}.
  +  Lock objects and exchange the references in collection obj_1{ref_2}
  +  and obj_2{ref_1} and commit --> FK values of ref_1 and ref_2 will not be updated.
  +- odmg-api: Creation of m:n relation only works when objects created step by step (or use
  +  as workaround), persist a whole object graph seems not to work proper.
  +- Batch handling doesn't work proper with optimistic locking. This will be fixed
  +  in version 1.1
  +- Subqueries are not extent aware. see QueryTest#testSubQueryAgainstExtents
  +- When using native Identity columns, OJB uses a temporary dummy value for created OJB
Identity objects
  +  of new pc objects (negative long values are used as dummy values for Identity columns,
the real value
  +  is available after the object insert), so the FK assignment is only valid after store
of the
  +  referenced object (PB-api handles this correctly). TransactionImpl#lock assign the FK
before the
  +  referenced object was written to DB. This only effects the ODMG API.
  +- Mapping of an inheritance hierarchy to multiple joined tables fails in the ODMG
  +  API only.
   Release 1.0.1

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message