ObjectDB ObjectDB

Internal Website Search

21-30 of 51 resultsRefresh
29

Remove not working

because, in the same transaction, I gather an Extent, delete an object, then try to gather the same Extent again. The Extent traversal throws the error because it encounters the object that was deleted. The fix was to do a PersistenceManager.flush() before trying to gather the Extent the second time. I did
1

javax.jdo.Query

extent, result class, and range limits are not used. The String parameters are trimmed of white ... is null, then the candidate collection is the extent of the candidate class. The String... version ... . Returns: the current setting of the flag Since: JDO 2.0 void setCandidates( Extent pcs) Set
1

getExtent(persistenceCapableClass, subclasses)

Method javax.jdo.PersistenceManager Extent<T> getExtent( Class<T> persistenceCapableClass, boolean ... on the class of the instances. This method returns an Extent of instances in the data store that might be iterated or given to a Query. The Extent itself might not reference any instances, but only hold
1

newQuery(cln, filter)

Method javax.jdo.PersistenceManager Query newQuery( Extent cln, String filter ) Create a new Query with the candidate Extent and filter; the class is taken from the Extent. Parameters: cln - the Extent of candidate instances filter - the filter for candidate instances Returns: the new Query Since: JDO 1.0
0

newQuery(cln)

Method javax.jdo.PersistenceManager Query newQuery( Extent cln ) Create a new Query with the Class of the candidate instances and candidate Extent. Parameters: cln - the Extent of candidate instances Returns: the new Query Since: JDO 1.0
0

setCandidates(pcs)

Method javax.jdo.Query void setCandidates( Extent pcs ) Set the candidate Extent to query. Parameters: pcs - the candidate Extent. Since: JDO 1.0
0

javax.jdo.FetchPlan

. An instance of this interface can be obtained from PersistenceManager.getFetchPlan, Extent.getFetchPlan, and Query.getFetchPlan. When a Query or Extent is retrieved from a PersistenceManager, its FetchPlan ... of the Query or Extent's FetchPlan are not reflected in the FetchPlan of the PersistenceManager. Since: JDO
0

addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters)

with a PersistenceManager, the candidate collection or extent, result class, and range limits are not used ... value is the empty String, or the parameter is null, then the candidate collection is the extent
0

javax.jdo.annotations.PersistenceCapable

requiresExtent Whether this class or interface manages an extent. Whether this class or interface manages an extent. Default value: "" Since: JDO 2.1 String schema Schema to use for persisting this class or
0

getExtent(persistenceCapableClass)

Method javax.jdo.PersistenceManager Extent<T> getExtent( Class<T> persistenceCapableClass ) Equivalent to getExtent (persistenceCapableClass, true). Parameters: persistenceCapableClass - Since: JDO 2.0 See Also: getExtent(Class,boolean)

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support