ObjectDB Database Search

51-100 of 200 results

jakarta.persistence.EntityManager.createQuery(String,Class)

Jakarta Persistence (JPA) Method in jakarta.persistence. EntityManager TypedQuery createQuery (    String qlString ,    Class resultClass ) Create an instance of TypedQuery for executing a Jakarta Persistence query language statement. The select list of the query must contain

jakarta.persistence.EntityManager.createNamedQuery(String)

Jakarta Persistence (JPA) Method in jakarta.persistence. EntityManager Query createNamedQuery (    String name ) Create an instance of Query for executing a named query written in the Jakarta Persistence query language or in native SQL. Parameters: name - the name of a query defined in

jakarta.persistence.EntityManager.createNamedQuery(String,Class)

Jakarta Persistence (JPA) Method in jakarta.persistence. EntityManager TypedQuery createNamedQuery (    String name ,    Class resultClass ) Create an instance of TypedQuery for executing a Jakarta Persistence query language named query. The select list of the query must contain

Obtaining a JPA Database Connection

In JPA, a database connection is represented by the EntityManager interface. Therefore, to manipulate an ObjectDB database, you need an EntityManager instance. Operations that modify database ... an EntityManager instance is a two-step process. First, you obtain an EntityManagerFactory instance

JPA Runtime Tuning & Configuration

): Defaults passed in a property map to the factory builder or defined in persistence.xml . EntityManager (session): Settings applied to an EntityManager instance override global defaults and affect ... defaults for that query. Operation (argument): Settings passed to specific EntityManager operations ( find

Setting and Tuning of JPA Queries

on which they were invoked. Flush mode (setFlushMode) Changes made to a database by using an EntityManager ... . However, these changes are not visible to users of other EntityManager instances. JPA implementations ... . The application can change the default mode at the EntityManager level, which applies to all queries in

EntityManager refresh problem

Hi, in the following code you can see an example with EntityManager .refresh(). The example ... -------------------- package example; import java.io.File; import javax.persistence. EntityManager ; import ... ;  public void refreshTest() {         EntityManager

UserException - Object User#2 belongs to another EntityManager

EntityManager with the same unitName. TradesC method needs an User, which is taken from UserDataB ... .pingushare.entity.p1.User#2' belongs to another EntityManager at com.objectdb.o.MSG.d(MSG.java:61 ... this should be a problem if, in the same transaction, an entity is passed into more EntityManagers , but here are 2

Pooling of EntityManagers

an internal pool of connections, and when an EntityManager is closed the underlying socket to the server is returned to the pool and can be reused with another new  EntityManager , as ... ; EntityManager holds is not preserved or reused. Is may be worth reusing these caches as well in some

Detached JPA Entities

Detached entities are objects in a special state where they are not managed by an EntityManager ... to the database unless you merge them back into an EntityManager , which makes them managed again. Detached objects are useful when an EntityManager is not available or for transferring objects between different

Retrieving JPA Entities

and its primary key. Given an EntityManager instance em , the following example retrieves an Employee ... class is not an entity class. If the EntityManager already manages the specified entity in ... is similar to the find method, but if the entity is not already managed by the EntityManager

EntityManagerFactory objects being locked during EntityManager creation

wherein the EntityManagerFactory objects are being locked during EntityManager object creation.  Please refer ... with ObjectDB wherein the EntityManagerFactory objects are being locked during EntityManager object creation.  This is the normal behavior of ObjectDB. Creation operations of  EntityManager

Object belongs to another EntityManager - ERROR

' belongs to another EntityManager (error 613) 10:29:14,887 ERROR [stderr] (http--10.23.3.98-8081-5 ... to another EntityManager 10:29:15,072 ERROR [stderr] (http--10.23.3.98-8081-5) at com.objectdb.o ... 'pbdmodel.impl.OrgJedinicaImpl#8' belongs to another EntityManager 10:29:15,089 ERROR [stderr] (http--10.23

EntityManager JPA or JDO impl and different behavior

Hi, I have an issue with the EntityManager . My persistance XML looks like: com.objectdb.jpa.Provider Now in our project we use spring to start everything. If I do: System.out.println(" EntityManager ... , I get: com.objectdb.jdo.PMImpl Whats going on here? Is the entityManager not controlled by

Attempt to execute a query using a closed EntityManager

. com.objectdb.o.UserException - Attempt to execute a query using a closed EntityManager at com ... to execute a query using a closed EntityManager at org.apache.myfaces.view.facelets.el ... .o._PersistenceException: Attempt to execute a query using a closed EntityManager at org.apache.el

EntityManager getMetamodel() causes crash

I am trying to track down some obscure errors with multi-threading.  This involved looking at the EntityManager Metamodel but this caused an ObjectDB exception.  So I reverted ... ;password=admin;drop" EntityManager em = emf.createEntityManager(); em.getTransaction().begin(); MyEntity

EntityManager creation taking long time

In our production environment, entity manager creation, the line below, sometimes take upto few ten's of seconds to create. Is there any reason that is known which may be causing this ? Any suggestions on how this can be addressed ?   EntityManager entityManager = factory.createEntityManager

Eclipse4 RCP - No Persistence provider for EntityManager

.PersistenceException: No Persistence provider for EntityManager I'm using the latest ObjectDB 2.6.2.b03 ... only this way (i.e. between building an EntityManagerFactory to building an EntityManager

EntityManager.refresh takes a long time

EntityManager .refresh takes a long time for entity object Person in this code:     logger.log(Level.INFO, "begin select for person " + new Date().toString());     ... level;   Does i understand this term correctly, if try to refresh Entitymanager updates

javax.persistence.PersistenceException: No Persistence provider for EntityManager named in Karaf 4.0.7 and OSGi DS test

.persistence.PersistenceException: No Persistence provider for EntityManager named objectdb

EntityManager.merge gives EntityNotFoundException

Just started using objectdb (2.3.4). Calling EntityManager .merge for a new (non-managed) object gives EntityNotFoundException. I am perplexed by this. See attached test case. Thanks for your assistance. Full error output is: Exception in thread "main" [ObjectDB 2.3.4] javax.persistence

Executing JUnit "all tests" throws "Object ... belongs to another EntityManager" Exception

.Symbol#7' belongs to another EntityManager [Symbol:7] When I change the order in which the test runs (by

multi EntityManager with Spring Boot, but 'Too many persistable types (>10)

I'm trying to use two EntityManager with Spring Boot, but no luck with 'Too many persistable types (10) - exceeds evaluation limit' at second database. My purpose is converting database (converting model entity. same class name but different package). Single application with Spring-Boot 2.1.8

DELETE Queries in JPA/JPQL

: Retrieve the entities into an EntityManager . Remove these objects from the EntityManager ... cautiously because bypassing the EntityManager can disrupt its synchronization with the database. For example, the EntityManager might not be aware that a DELETE query has removed an entity

JPA Container Injection Annotations

the container to inject EntityManager or EntityManagerFactory proxies directly into application components such as services and DAOs. EntityManager injection Inject an EntityManager and configure its scope using the following annotations: Expresses a dependency on a container-managed EntityManager , injecting

Query Parameters in JPA

a Country object from the database by its name: public Country getCountryByName( EntityManager em ... ( EntityManager em, String name) { TypedQuery query = em. createQuery ( "SELECT c FROM Country c WHERE c.name ... , this time without parameters: public Country getCountryByName( EntityManager em, String name

jakarta.persistence.EntityManagerFactory

of EntityManager . A persistence unit defines the set of all classes that are related or grouped by ... -managed EntityManager may be created via a call to createEntityManager . However, this approach places ... EntityManager s. Alternatively, in the Jakarta EE environment, a container-managed EntityManager

JPA Lifecycle Events

when the EntityManager detects that an entity has been modified. @PostUpdate : Invoked after an entity ... with the database operation that triggers the event, callback methods must not call EntityManager or Query methods

SELECT clause (JPQL / Criteria API)

The ability to retrieve managed entities is a key advantage of JPQL. For example, the following query returns Country objects, which then become managed by the EntityManager instance em : TypedQuery ... are not associated with an EntityManager , and changes to them during an active transaction are not

Storing JPA Entities

, and its initial state is New. An explicit call to persist associates the object with an owner EntityManager , em ... the EntityManager , or by commit . Referenced embedded objects The following code stores an Employee instance

JPA Queries

EntityManager  methods such as createQuery to build  query objects using: Direct JPQL query strings ... ; EntityManagerFactory or   EntityManager  using the getCriteriaBuilder method. Additional

JPA Query API

with createQuery As with most JPA operations, queries start with an EntityManager (represented as em in the following code snippets). The EntityManager serves as a factory for both Query

JPA Named Queries Annotations

. Retrieve it by result type from EntityManagerFactory.getNamedQueries , and use it to get a TypedQuery instance via EntityManager .createQuery .

JPA Named Queries

, but you use different EntityManager factory methods to instantiate them. The createNamedQuery method

JPA Core Types

: A heavyweight factory class responsible for creating EntityManager instances. Create

JPA Criteria Queries

to EntityManager .createQuery to obtain a TypedQuery . For nested queries within a main query, use

CRUD Database Operations with JPA

Given an EntityManager instance, em , which manages the persistence context for the database, you can use it to store, retrieve, update, and delete objects. Storing new entities The following code fragment stores 1,000 Point objects in the database: em. getTransaction (). begin (); for (int i = 0

jakarta.persistence.EntityNotFoundException

by the persistence provider when an entity reference obtained by EntityManager .getReference is accessed but the entity does not exist. Thrown when EntityManager .refresh is called and the object no longer exists in the database. Thrown when EntityManager .lock is used with pessimistic locking is used

jakarta.persistence.EntityGraph

. See Also: AttributeNode Subgraph NamedEntityGraph EntityManager .createEntityGraph(Class) EntityManager .createEntityGraph(String) EntityManager .getEntityGraph(String) EntityManagerFactory.addNamedEntityGraph(String, EntityGraph) EntityManager .find(EntityGraph, Object, FindOption...) Since: Jakarta

An entityManager.flush() with many entities is not possible

  The following exception occures if we call entityManager .flush() where the corresponding JPA PersistenceContext has many entities and relations. What is the reason for the exception? entityManager .getTransaction().commit() instead of a entityManager .flush() works correctly. Unfortunately I

jakarta.persistence.NamedEntityGraph

. A reference to a named entity graph may be obtained by calling EntityManager .getEntityGraph , and may be passed to EntityManager .find . Since: Jakarta Persistence (JPA) 2.1 Annotation Elements String name (Optional) The name used to identify the entity graph in calls to EntityManager .getEntityGraph

jakarta.persistence.FindOption

Jakarta Persistence (JPA) Interface jakarta.persistence.FindOption An option influencing the behavior of EntityManager .find . Built-in options control locking , cache interaction , and timeouts ... Timeout EntityManager .find(Class, Object, FindOption...) EntityManager .find(EntityGraph, Object, FindOption...) Since: Jakarta Persistence (JPA) 3.2

Step 3: Define an EJB Session Bean

java.util.List; import javax.ejb.Stateless; import javax.persistence. EntityManager ; import javax ... { // Injected database connection: @PersistenceContext private EntityManager em; // Stores a new guest ... ). Prepares an  EntityManager automatically and injects it into the  em field

Step 3: Define a Spring DAO Component

; import javax.persistence. EntityManager ; import javax.persistence.PersistenceContext; import javax ... connection: @PersistenceContext private EntityManager em; // Stores a new guest: @Transactional public ... the controller, as shown in the next step. Prepares an  EntityManager automatically and injects it into

Step 3: Define a Spring DAO Component

.List; import javax.persistence. EntityManager ; import javax.persistence.PersistenceContext; import ... connection: @PersistenceContext private EntityManager em; // Stores a new guest: @Transactional public ... the controller, as shown in the next step. Prepares an  EntityManager automatically and injects it into

Step 4: Add a Servlet Class

)getServletContext().getAttribute("emf"); EntityManager em = emf.createEntityManager(); try { // Handle ... is retrieved from the application scope attribute, and then an EntityManager (representing a database

Step 6: Set the Spring XML

and transactions), to inject a JPA  EntityManager , to manage transactions and to look for JSP pages in

Step 6: Set the Spring XML

, controllers and transactions), to inject a JPA EntityManager , to manage transactions and to look

Step 3: Add a Main Class

;          "$objectdb/db/p2.odb"); EntityManager em

Step 3: Add a Main Class

;        "$objectdb/db/p2.odb"); EntityManager em = emf