db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Update of "CurrentDevelopment" by MichelleCaisse
Date Fri, 08 Dec 2006 20:24:35 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jdo Wiki" for change notification.

The following page has been changed by MichelleCaisse:
http://wiki.apache.org/jdo/CurrentDevelopment

------------------------------------------------------------------------------
  || 23 || In 12.7.6 p. 129, change fetch-depth to recursion-depth in the example. || x ||
|| ||
  || 24 || In 14, add subqueries to permit e.g. select from Employee where this.salary >
(select avg(salary) from Employee) || x || x || x ||
  || 25 || In 14.6.2 p. 159, the sectionheading "Methods" is not marked as a sectionheading.
|| x || || ||
- || 26 || Add to 14.6.9: Projected SCOs are never owned, projected FCOs are always managed.
Modifying unowned SCOs never has an effect on the database. Modifying FCOs no matter how you
get them always has an effect if the tx commits. || x || || http://issues.apache.org/jira/browse/JDO-390
||
+ || 26 || Add to 14.6.9: Projected SCOs are never owned, projected FCOs are always managed.
Modifying unowned SCOs never has an effect on the database. Modifying FCOs no matter how you
get them always has an effect if the tx commits. || x || || [http://issues.apache.org/jira/browse/JDO-390
JDO-390]||
  || 27 || In 15.3, p. 187, the third paragraph, beginning "The field on the other side" and
ending "in the next transaction", is duplicated and will be removed. || x || || ||
  || 28 || In 15.3, add text to describe updating the other side of relationships where this
side is deleted. This maintains referential integrity for delete as well as update. || x ||
|| x ||
  || 29 || Add to 17.1.11 JDO!UserCallbackException extends javax.jdo.JDO!UserException ||
x || x || x ||
@@ -43, +43 @@

  || 38 || Change 21.21.7 Generated jdoGetManagedFieldCount sample implementation to avoid
using the jdoFieldNames field that might be initialized after it is used during initialization
of a subclass. (See ChangeLog for details.) || x || || ||
  || 39 || Add to Chapter 23, constants defined in the JDOPermission class. (See ChangeLog
for details.) || x || || ||
  ||40 || JDK 1.5 changes || x || || ||
- || 41 || Add to 6.3 a section requiring support for enum types, including subclasses of
enum types. || x || x || x ||
+ || 41 || Add to 6.3 a section requiring support for enum types, including subclasses of
enum types. || x || || x ||
  || 42 || Change in 12.6 signatures of the following !PersistenceManager methods to be generic.
Note that these changes are source compatible with existing application programs. (See ChangeLog
for details.) || x || x || x ||
  || 43 || Add to 15.1 a paragraph describing that mapping an enum to a fixed-precision numeric
type uses the ordinal() value for storage; mapping to a character column type (CHAR, VARCHAR,
etc.) uses the name() value for storage; mapping to any other column type is an error. ||
x || || x ||
  || 44 || Provide in a new chapter a set of annotations that map directly to xml elements
as an alternative to using xml metadata. Describe how jdo implementations can use either JDO
annotations or JPA annotations to provide metadata. || x || x || x ||

Mime
View raw message