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 Thu, 10 Jun 2004 14:12:00 GMT
arminw      2004/06/10 07:12:00

  Modified:    .        release-notes.txt
  Log:
  add more known issues
  
  Revision  Changes    Path
  1.45      +21 -13    db-ojb/release-notes.txt
  
  Index: release-notes.txt
  ===================================================================
  RCS file: /home/cvs/db-ojb/release-notes.txt,v
  retrieving revision 1.44
  retrieving revision 1.45
  diff -u -r1.44 -r1.45
  --- release-notes.txt	6 Jun 2004 19:52:06 -0000	1.44
  +++ release-notes.txt	10 Jun 2004 14:12:00 -0000	1.45
  @@ -55,27 +55,35 @@
   and obj_2{ref_2}. Lock objects and exchange the references in collection obj_1{ref_2}
   and obj_2{ref_1} and commit.
   
  +- odmg-api: Creation of m:n relation only works when objects created step by step (or use
PB-api
  +as workaround), persist a whole object graph doesn't work. On delete of collection objects
from a m:n relation
  +objects will be deleted from the indirection table and (unexpected behaviour) from the
referenced
  +table too.
  +
   - ReportQueries should not be used with columns referencing Classes with extents:
   
  -ReportQueryByCriteria q = QueryFactory.newReportQuery(ProductGroup.class, crit);
  -q.setAttributes(new String[] { "groupName", "sum(allArticlesInGroup.stock)", "sum(allArticlesInGroup.price)"
});
  -q.addGroupBy("groupName");
  +    ReportQueryByCriteria q = QueryFactory.newReportQuery(ProductGroup.class, crit);
  +    q.setAttributes(new String[] { "groupName", "sum(allArticlesInGroup.stock)", "sum(allArticlesInGroup.price)"
});
  +    q.addGroupBy("groupName");
   
  -ProductGroup.allArticlesInGroup points to class Article having multiple extents.
  +    ProductGroup.allArticlesInGroup points to class Article having multiple extents.
   
  -As a workaround the query can be 'reversed' :
  +    As a workaround the query can be 'reversed' :
   
  -ReportQueryByCriteria q = QueryFactory.newReportQuery(Article.class, crit);
  -q.setAttributes(new String[] { "productGroup.groupName", "sum(stock)", "sum(price)" });
  -q.addGroupBy("productGroup.groupName");
  +    ReportQueryByCriteria q = QueryFactory.newReportQuery(Article.class, crit);
  +    q.setAttributes(new String[] { "productGroup.groupName", "sum(stock)", "sum(price)"
});
  +    q.addGroupBy("productGroup.groupName");
   
  -Due to the fact the Article has extents multiple selects will be executed, 
  -so the same ProductGroup may show up more than once.
  +    Due to the fact the Article has extents multiple selects will be executed,
  +    so the same ProductGroup may show up more than once.
   
  -Please see the testcases QueryTest#testReportQueryGroupByExtents1 and 
  -QueryTest#testReportQueryGroupByExtents2. 
  +    Please see the testcases QueryTest#testReportQueryGroupByExtents1 and
  +    QueryTest#testReportQueryGroupByExtents2.
   
   - A count on ReportQueries containing groupBy does not deliver a correct result.
  +
  +- Batch handling doesn't work proper with optimistic locking. This will be fixed
  +before long after 1.0
   
   ---------------------------------------------------------------------
   Release 1.0 rc6
  
  
  

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