db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bri...@apache.org
Subject cvs commit: db-ojb build.properties release-notes.txt
Date Wed, 08 Sep 2004 20:06:38 GMT
brianm      2004/09/08 13:06:38

  Modified:    .        Tag: OJB_1_0_RELEASE build.properties
                        release-notes.txt
  Log:
  Update version in build.properties
  Update known issues in release notes
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.64.2.2  +3 -3      db-ojb/build.properties
  
  Index: build.properties
  ===================================================================
  RCS file: /home/cvs/db-ojb/build.properties,v
  retrieving revision 1.64.2.1
  retrieving revision 1.64.2.2
  diff -u -r1.64.2.1 -r1.64.2.2
  --- build.properties	26 Aug 2004 00:00:39 -0000	1.64.2.1
  +++ build.properties	8 Sep 2004 20:06:38 -0000	1.64.2.2
  @@ -168,9 +168,9 @@
   project-name=db-ojb
   major=1
   minor=0
  -build=0
  +build=1
   version=${major}.${minor}.${build}
  -versiondate=2004-06-25
  +versiondate=2004-09-08
   ojb-filename-prefix=${project-name}-${version}
   
   #
  
  
  
  1.54.2.7  +8 -4      db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.54.2.6
  retrieving revision 1.54.2.7
  diff -u -r1.54.2.6 -r1.54.2.7
  --- release-notes.txt	27 Aug 2004 19:41:55 -0000	1.54.2.6
  +++ release-notes.txt	8 Sep 2004 20:06:38 -0000	1.54.2.7
  @@ -73,9 +73,13 @@
   - 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
  
  
  

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


Mime
View raw message