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 "AllTheOtherTests" by CraigRussell
Date Sun, 02 Oct 2005 13:19:32 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 CraigRussell:
http://wiki.apache.org/jdo/AllTheOtherTests

------------------------------------------------------------------------------
  ||PM||A12.7.1-2||A12.7.1-2 [/** Set detachment options */ Fetch``Plan setDetachmentOptions(int
options); /** Return the detachment options */ int getDetachmentOptions();]]||.||.||
  ||PM||A12.8-2||A12.8-2 [void flush(); This method flushes all dirty, new, and deleted instances
to the datastore. It has no effect if a transaction is not active. If a datastore transaction
is active, this method synchronizes the cache with the datastore and reports any exceptions.
If an optimistic transaction is active, this method obtains a datastore connection and synchronizes
the cache with the datastore using this connection. The connection obtained by this method
is held until the end of the transaction..]||.||.||
  ||PM||A12.8-3||A12.8-3 [void checkConsistency(); This method validates the cache with the
datastore. It has no effect if a transaction is not activeIf a datastore transaction is active,
this method verifies the consistency of instances in the cache against the datastore. An implementation
might flush instances as if flush() were called, but it is not required to do so If an optimistic
transaction is active, this method obtains a datastore connection and verifies the con­sistency
of the instances in the cache against the datastore. If any inconsistencies are detected,
a JDOOptimistic``Verification``Exception is thrown. This exception contains a nested JDOOptimistic``Verification``Exception
for each object that failed the consistency check. No datastore resources acquired during
the execution of this method are held beyond the scope of this method.]||.||.||
- ||PM||A12.11-1||A12.11-1 [Object putUserObject(Object key, Object value); This method models
the put method of Map. The current value associated with the key is returned and replaced
by the parameter value. If the parameter value is null, the implementation may re­move the
entry from the table of managed key/value pairs Object removeUserObject(Object key); This
method models the remove method of Map. The current value associated with the key is re­turned
and removed Object getUserObject(Object key); This method models the get method of Map. The
current value associated with the key is returned. If the key is not found in the table, null
is returned.]..]||.||.||
+ ||PM||A12.11-1||A12.11-1 [Object putUserObject(Object key, Object value); This method models
the put method of Map. The current value associated with the key is returned and replaced
by the parameter value. If the parameter value is null, the implementation may re­move the
entry from the table of managed key/value pairs Object removeUserObject(Object key); This
method models the remove method of Map. The current value associated with the key is re­turned
and removed Object getUserObject(Object key); This method models the get method of Map. The
current value associated with the key is returned. If the key is not found in the table, null
is returned.]..]||clr||JDO-154||
  ||PM||A12.12-1||A12.12-1 [The application might need to get the Persistence``Manager``Factory
that created this Persistence``Manager. If the Persistence``Manager was created using a constructor,
then this call returns null.]]||.||.||
  ||PM||12.5.6-18||12.5.6-18 [Object getObjectById (Class cls, Object key); The getObjectById
method attempts to find an instance in the cache with the derived JDO identity. The key parameter
is either the string representation of the object id, or is an object repre­sentation of
a single field identity key.]]||.||.||
  ||PM||12.5.6-17||12.5.6-17 [Collection getObjectsById (Collection oids); Object[] getObjectsById
(Object[] oids); Collection getObjectsById (Collection oids, boolean validate); Object[] getObjectsById
(Object[] oids, boolean validate); The getObjectsById method attempts to find instances in
the cache with the specified JDO identities. The elements of the oids parameter object might
have been returned by earlier calls to getObjectId or getTransactionalObjectId, or might have
been constructed by the application.  If a method with no validate parameter is used, the
method behaves exactly as the correspond­ing method with the validate flag set to true. If
the Object[] form of the method is used, the returned objects correspond by position with
the object ids in the oids parameter. If the Collection form of the method is used, the iterator
over the returned Collection returns instances in the same order as the oids returned by an
iterator over the parameter Collection. The card
 inality of the return value is the same as the cardinality of the oids parameter. ]||.||JDO-141||

Mime
View raw message