ObjectDB Database Search

Customer asked during opened ObjectDb connection (ODB location A) to stop writing and continue to another ODB file (Location B). Does exist some API to achieve that? What is a possible solution? Harman Alexander Golyshkin You have to close the database in location A, copy it from location

Is there an API to get the current version of ObjectDB that's being used? This would be very handy to have, because it is somewhat difficult to know what version of the ObjectDB you are currently using since the objectdb.jar filename remains the same for all versions (which is not a bad thing by

(JpaQuery.java:719) - locked (a com.objectdb.jdo.PMImpl) at com.agile.hummingbird. API .handleQuery( API .java:3020) at com.agile.hummingbird. API .directRequest( API .java:852) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:614) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

Issue with TYPE expression in Criteria API

criteria api / embedded objects / where order

that is specific to top-level queries. Since: JPA 2.0 The JPA Criteria API Queries article explains how to use ... : Applications using the string-based API may need to specify the type of the select item when it results from

JPA Interface CriteriaDelete Type Parameters: - the entity type that is the target of the delete Super Interfaces: CommonAbstractCriteria The CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria API Criteria API bulk delete operations map directly

APIs can be overridden. Information that is overridden does not affect the named query as registered ... of the specified type to allow access to the provider-specific API . If the provider's EntityManagerFactory

is found not to be a Java Persistence query language SELECT query or a Criteria API query Since: JPA 2.0 ... of the specified type to allow access to the provider-specific API . If the provider's query

SELECT query or a Criteria API query Inherited from: Query Since: JPA 2.0 int getMaxResults ... API . If the provider's query implementation does not support the specified class

. Within the persistence context, the entity instances and their lifecycle are managed. The EntityManager API is used ... of the specified type to allow access to the provider-specific API . If the provider's EntityManager

JPA Interface CriteriaBuilder Used to construct criteria queries, compound selections, expressions, predicates, orderings. Note that Predicate is used instead of Expression in this API in order ... Criteria API Queries article explains how to use CriteriaBuilder . Public Methods Expression abs

- if the query is found not to be a Java Persistence query language SELECT query or a Criteria API ... of the specified type to allow access to the provider-specific API . If the provider's query

" expression. Since: JPA 2.0 The Paths and Types in JPQL and Criteria API article explains ... corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify

JPA Interface CriteriaUpdate Type Parameters: - the entity type that is the target of the update Super Interfaces: CommonAbstractCriteria The CriteriaUpdate interface defines functionality for performing bulk update operations using the Criteria API . Criteria API bulk update operations map

.hummingbird.CT_Container.computeContainer(CT_Container.java:214) com.agile.hummingbird. API .handleGetContainer( API .java:3130) com.agile.hummingbird. API .directRequest( API .java:965) com.agile.hummingbird. API .handleWebSocketRequest( API .java:808) com.agile.hummingbird.WebSocketServerListener

JPA Interface Selection Type Parameters: - the type of the selection item Super Interfaces: TupleElement The Selection interface defines an item that is to be returned in a query result. Since: JPA 2.0 The SELECT clause (JPQL / Criteria API ) article explains how to use Selection . Public Methods

JPA Interface Root Type Parameters: - the entity type referenced by the root Super Interfaces: FetchParent , From A root type in the from clause. Query roots always reference entities. Since: JPA 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Root . Public Methods EntityType

part of an API call, at, flush or at commit time. The current transaction, if one is active, will be not

JPA Method in javax.persistence.EntityManagerFactory T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's EntityManagerFactory implementation does not support the specified class, the PersistenceException

when an pessimistic locking conflict occurs. This exception may be thrown as part of an API call, a flush or at commit

and Criteria API article explains how to use Predicate . Public Methods List getExpressions () Return

JPA Method in javax.persistence.criteria.Path Path get (   String attributeName ) Create a path corresponding to the referenced attribute. Note: Applications using the string-based API may need to specify the type resulting from the get operation in order to avoid the use of Path

is executed, information that can be set by means of the query APIs can be overridden. Information

locking conflict occurs. This exception may be thrown as part of an API call, a flush or at commit

well; however, support for the Java SE bootstrapping APIs is not required in container environments

JPA Method in javax.persistence.Query T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's query implementation does not support the specified class, the PersistenceException is thrown. Parameters: cls

JPA Method in javax.persistence.Query LockModeType getLockMode () Get the current lock mode for the query. Returns null if a lock mode has not been set on the query object. Return: lock mode Throws: IllegalStateException - if the query is found not to be a Java Persistence query language SELECT query or a Criteria API query Since: JPA 2.0

corresponding to the referenced attribute. Note: Applications using the string-based API may need

JPA Interface Order An object that defines an ordering over the query results. Since: JPA 2.0 The ORDER BY clause (JPQL / Criteria API ) article explains how to use Order . Public Methods Expression getExpression () Return the expression that is used for ordering. Return: expression used

JPA Annotation Attribute in javax.persistence.SqlResultSetMapping String name default null The name given to the result set mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs . Since: JPA 1.0

to the result set mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs . Since: JPA 1.0

JPA Method in javax.persistence.Cache T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's Cache implementation does not support the specified class, the PersistenceException is thrown. Parameters: cls

to allow access to the provider-specific API . If the provider's Cache implementation does not support

JPA Method in javax.persistence.EntityManager T unwrap (   Class  cls ) Return an object of the specified type to allow access to the provider-specific API . If the provider's EntityManager implementation does not support the specified class, the PersistenceException is thrown

JPA Interface Join Type Parameters: - the source type of the join - the target type of the join Super Interfaces: Expression , FetchParent , From , Path A join to an entity, embeddable, or basic type. Since: JPA 2.0 The FROM clause (JPQL / Criteria API ) article explains how to use Join . Public

JPA Method in javax.persistence.criteria.CriteriaQuery CriteriaQuery select (   Selection  selection ) Specify the item that is to be returned in the query result. Replaces the previously specified selection(s), if any. Note: Applications using the string-based API may need

.endAction(AC_Action.java:878) at com.agile.hummingbird. API .executeEndAction( API .java:1874) at com.agile.hummingbird. API .handleAction( API .java:1614) at com.agile.hummingbird. API .directRequest( API .java:1089) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:890) at com.agile.hummingbird

I am running a stress test with 2 users, each making a request to the JSON API (which uses as storage ObjectDB) each 50 milliseconds. An API call might have between 1-4 db calls ... ) at com.fitbird.boundary. api .util.PlanAccessVerifier. (PlanAccessVerifier.java:40) at com.fitbird.boundary

.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment) $1.qubletFRAGMENTMAP.get('com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied.MitgliedDebitorenKontoFragment')).debitor=true)) AND ((((com.lexware.vereinsverwaltung.abrechnung. api .model.mitglied

.hummingbird. API .executeEndAction( API .java:1718) at com.agile.hummingbird. API .handleAction( API .java:1480) at com.agile.hummingbird. API .directRequest( API .java:1001) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:836) at com.agile.hummingbird.WebSocketServerListener.onWebSocketText

.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API .directRequest( API .java:802) at com.agile.hummingbird. API .handleWebSocketRequest( API .java:630) at com.agile.hummingbird ... .java:163) at com.agile.hummingbird. API .handleGetContainer( API .java:2745) at com.agile.hummingbird. API

, and the array is modified, then the persistent instance is not aware of the change. This API ... the same field, and if the package and class name are not provided by the parameter in this API

of the change. This API allows the application to notify the instance that a change was made to a field ... in this API , then the field marked dirty is the field declared by the most derived class. Transient

instance is not aware of the change. This API allows the application to notify the instance that a change

is not aware of the change. This API allows the application to notify the instance that a change

the default fetch group via the API does not affect the members defined by this category. Using this category

JDO Static Field in javax.jdo.FetchGroup DEFAULT For use with addCategory and removeCategory calls. This category includes members defined in the default fetch group in xml or annotations. Redefining the default fetch group via the API does not affect the members defined by this category. Using

is modified, then the persistent instance is not aware of the change. This API allows the application

, then the persistent instance is not aware of the change. This API allows the application to notify the instance