 3 | to prefix the name of the attribute within the embeddable class that is being overridden by order ... that extends a mapped superclass to override a relationship mapping defined by the mapped superclass ... a mapping defined by a mapped superclass, AssociationOverride is applied to the entity class |
3 | levels might be supported by an implementation but are not standard. Standard values in order ... a transaction. Begin a transaction. The type of transaction is determined by the setting of the Optimistic flag. Throws: JDOUserException - if transactions are managed by a container in the managed |
3 |
{
@OneToMany // the annotation is not required by ObjectDB
Vector<Order> orders;
}
@Entity ... . By the way, if you define the reference in Order, you can use an inverse / mapped-by field in ... and be statically typed. For example: Assume there are Customers and Orders. with JDO I |
3 | of this form means that instances of all persistence-capable classes will be observed by an instance ... values not recognized by the implementation must be ignored. Key values that are recognized but not supported by an implementation must result in a JDOFatalUserException thrown by the method. The returned |
3 | for PessimisticLockScope.NORMAL, element collections and relationships owned by the entity ... , element collections and relationships owned by the entity that are contained in join tables ... of PessimisticLockScope.EXTENDED. The state of entities referenced by such relationships will not be locked (unless |
3 | . For step by step instructions on using BIRT with ObjectDB see the Report Generation with BIRT ... extension. To install it: Open the [Install] dialog box by selecting Help > Install New Software... In ... ENTER. Select the ObjectDB Birt/ODA feature. Complete the installation by clicking Next twice, accepting |
3 | are represented in criteria queries by descendant interfaces of the From interface: Range variables (bound by an entity class) are represented by the Root subinterface: Join variables (bound by an attribute of a preceding variable in the FROM clause) are represented by the Join subinterface |
3 | . Recording is enabled by default and can be disabled in the configuration. The ObjectDB Replayer tool ... is useful for two different purposes: It enables recovery from a database failure by replaying the recorded operations. It enables reproducing problems during debugging by repeating a failure. Backup |
3 | , if an ObjectDB database is accessed directly only by a web application, it should be embedded in ... . This can be overridden by specifying a configuration path explicitly on the command line:
> java com.objectdb ... is also specified in the Server Configuration, but can be overridden by an explicit command line |
3 | Metamodel API is Metamodel. It can be obtained either by the EntityManagerFactory's getMetamodel method or by the EntityManager's getMetamodel method (both methods are equivalent). For example, given an EntityManager, em, a Metamodel instance can be obtained by:
Metamodel metamodel = em.getMetamodel |