ObjectDB Database Search

retrieve it using an Extent everything is present. We have a very simple class: public class ... is there. If I call Extent extent =     pm.getExtent(PositionReportManagerBean.class, true); I get an Extent back with all of the data as I would expect. However, if I execute a Query

against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial ... to the minimum extent necessary to make such provision valid and enforceable. If Recipient institutes patent

to the extent necessary to comply with our legal obligations (for example, if we are required

an entity object that is represented by a child of an Extent node in a viewer window deletes

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

this code: pm.currentTransaction().begin(); Extent extent = pm.getExtent(ABC.class, true); Query q = pm.newQuery( extent ); long deletedCount = q.deletePersistentAll(); pm.currentTransaction().commit ... (bookmarks). Instead of the above code, I could iterate over the Extent and delete the entities

files. In those metadata files I have few persistence-capable classes which had extents in ObjectDB 1 (with an OID for every instance) and all other classes were embedded (so without extent ... as not embedded, with own extent and OID for every instance. So my questions are: 1

I am having trouble with the Explorer.  I can open the db just fine. I can open a few simple extents and view/navigate fine also.  The problem occurs when I view the more complex extents . The Explorer will not repaint the right pane.  I drag off screen to force repaint and get(right

) is preferred. Regarding Extent in JPA, your "SELECT a FROM User a" query is the standard replacement of JPA for JDO extents . Alternatively, if you want, you may use JDO from JPA application by obtaining

you can see the classes are not embedded, so they have their own extent and IDs in the DB

per relationship, and for some extent also per query (using JOIN FETCH ). support Support

step; btc_es BTC EmbeddedSystems To some extent , yes, but it depends. For example, are the long values

read the database file header). To some extent it is affected by the number of persistent types in

this further and we will also be able to check the second query. Your other questions are covered, at least to some extent in

classes with ObjectDB may work to some extent . You can use a generics class parameter as the type

exactly the same code modifications. There may be a difference with the extent of enhanced code. Automatic

entries in the Address extent , i.e. there is a duplicate entity that is not related to any

Fixed a bug in persisting objects with same ids in a class hierarchy in one transaction. Fixed a bug in using JDO Extent of a super class with shared primary key values in subclasses. Added a warning if a JDO SingleFieldIdentity class is used as a primary key field type.

with ObjectDB may work to some extent . You can use a generics class parameter as the type of a persistent