ObjectDB ObjectDB

Internal Website Search

31-40 of 172 resultsRefresh
13

IDs of Entities suddenly became UUIDs?

Hi, We're having our system with ObjectDB 2.4.5 in production since this year April and it works ... Objects in the DB are having the field "myId" as type "String" and with an UUID ... that all Databases we use are affected by this. Many of them having mixed Long and UUID String ids
13

JPQL query to get entities that does not have a child entity in their child entities

_Started        2105:12:10 14:00:00      004 From these 2 tables I have to query for Jobs having states FINISHED, CANCELED, FAILED and ACTIVE. FINISHED: A Job having status 'Finished'. CANCELED: A Job having status '%Canceled' and not ('Finished'). FAILED: A Job having status '%Failed' and not
12

Updating Entities

' and all the changes take place naturally as intended. That said - I don't like the fact that I'm having to cycle ... OK. Note that having a separate object context for every EntityManager is a very basic principle ... to this is having to collect each object that needs to have its reference updated and then update the object
3

getGroupRestriction()

Method javax.persistence.criteria.AbstractQuery Predicate getGroupRestriction() Return the predicate that corresponds to the restriction(s) over the grouping items, or null if no restrictions have been specified. Returns: having clause predicate Since: JPA 2.0
0

getUserObject()

Method javax.jdo.PersistenceManager Object getUserObject() The application can manage the PersistenceManager instances more easily by having an application object associated with each PersistenceManager instance. Returns: the user object associated with this PersistenceManager Since: JDO 1.0 See Also: setUserObject
0

javax.jdo.listener.InstanceLifecycleListener

can be defined to use a life-cycle listener pattern instead of having the domain class implement the callback interface(s). Since: JDO 2.0
0

javax.jdo.spi.JDOImplHelper

this class only if they are authorized by the security manager. To avoid having
0

getManagedObjects(states)

Method javax.jdo.PersistenceManager Set getManagedObjects( EnumSet<ObjectState> states ) Get the objects managed by this persistence manager having the specified object states. Parameters: states - The states of objects that we are interested in Returns: the objects Since: JDO 2.1
0

getManagedObjects(states, classes)

Method javax.jdo.PersistenceManager Set getManagedObjects( EnumSet<ObjectState> states, Class... classes ) Get the objects managed by this persistence manager having the specified object states and being instances of the specified classes. Parameters: states - The states of objects
0

setUserObject(o)

Method javax.jdo.PersistenceManager void setUserObject( Object o ) The application can manage the PersistenceManager instances more easily by having an application object associated with each PersistenceManager instance. Parameters: o - the user instance to be remembered by the PersistenceManager Since: JDO 1.0 See Also: getUserObject

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