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, 14 Aug 2004 23:57:57 GMT
arminw      2004/08/14 16:57:57

  Modified:    .        Tag: OJB_1_0_RELEASE release-notes.txt
  Log:
  update notes
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.54.2.4  +8 -2      db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.54.2.3
  retrieving revision 1.54.2.4
  diff -u -r1.54.2.3 -r1.54.2.4
  --- release-notes.txt	27 Jul 2004 23:40:01 -0000	1.54.2.3
  +++ release-notes.txt	14 Aug 2004 23:57:56 -0000	1.54.2.4
  @@ -28,6 +28,9 @@
     result set and check against the cache. If no match map all field values
     from result set to internal Map class (old version always maps all values
     from the result set to the internal Map class).
  +- add in ObjectCacheDefaultImpl new attribute 'cachingKeyType' this allows to
  +  differ cached objects of same class for different databases.
  +  http://nagoya.apache.org/eyebrowse/ReadMsg?listName=ojb-user@db.apache.org&msgNo=13931
   
   BUG FIXES:
   Please refer to our Bug tracking site (http://issues.apache.org/scarab/servlet/scarab/)
  @@ -48,8 +51,11 @@
   - ojb no longer adds groupBy columns to the SELECT-clause, orderBy columns are still added
because of sapdb
   - orderBy columns of the original query are used as joinAttributes in count-query
   - ALIAS-prefix again works for report-queries (see QueryTest#testReportQueryAlias)
  -- odmg-api: fix problem with TransactionExt#flush() call, always check for
  +- odmg-api: Fix problem with TransactionExt#flush() call, always check for
     changed objects
  +- odmg-api: Fix issue with FK assignment, referenced proxy object should not be materialized
to assign
  +  FK in main object.
  +- odmg-api: Fix Database#open(...) issue. In managed environments now no running JTA-tx
was expected  
   
   KNOWN ISSUES:
   - odmg-api: If a user exchange already existing objects in 1:n references without changing
the size
  
  
  

---------------------------------------------------------------------
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