About modified

forum_thread

JPQL IN Operator

How can I use the standard JPQL IN operator with ObjectDB? This JPQL query works fine with EclipseLink / postgres but throws an exception in objectDB: select distinct dv.creationtime from DataValue dv where dv.capabilityId.capabilityId ==> in <== :capabilities and dv.creationtime >= :earliest and dv.creationtime <= :latest order by dv.creationtime ASC [ObjectDB 2.2.9] javax.persistence.PersistenceException Unexpected query token 'in' (error 752) ... thanks for suggestion, I modified the queries to read e.g. as follows: @NamedQuery ( name ...

 
forum_thread

pesimistic Lock semantic

Hi   I have tested pesimistic lock and the result was for me unexpected. In the first transaction i modified one object and in the second transaction i wanted to the same and  I got an exceptopn that lock could not be granted, quite nice but in that moment I wanted commit the first transaction and I also got lock exception. this the test:   public void testPesimisticLock() {   PersistenceManager pm1 = null;   PersistenceManager pm2 = null; ... result was for me unexpected. In the first transaction i modified one object and in the second transaction i wanted to the same ...

 
api-jdo

jdoPreClear()

Called before the values in the instance are cleared.(Method of javax.jdo.listener.ClearCallback)

 
api-jdo

javax.jdo.listener.DeleteCallback

This interface is used to notify instances of delete events.(Interface of JDO)

 
api-jpa

multiselect(selections)

Specify the selection items that are to be returned in the query result.(Method of javax.persistence.criteria.CriteriaQuery)

 
api-jdo

preClear(event)

This method is called before the implementation calls the instance method ClearCallback.jdoPreClear and before it clears the values in the instance to their Java default values.(Method of javax.jdo.listener.ClearLifecycleListener)

 
forum_thread

Querys slower when execute a query after every persist

The test case of the java file attachment persists many entities and executes a query after every persist. The execution time amounts 2 sec when the test persists 1000 entities. The execution time amounts 100 sec when the test persists 10000 entities. We have been expected that the second case requires only 20 sec, but the test requires 100 sec. Why the querys will be more and more slower? In addition there are a cpu snapshot for visual vm and an image of cpu snapshot as attachment. ... to find which objects in the persistence context have been modified and should be flushed to the database. If you have more objects in the ...

 
api-jpa

javax.persistence.spi.ClassTransformer

A persistence provider supplies an instance of this interface to the PersistenceUnitInfo.addTransformer method.(Interface of JPA)

 
api-jdo

makeTransactional(pc)

Make an instance subject to transactional boundaries.(Method of javax.jdo.PersistenceManager)

 
api-jdo

makeDirty(pc, fieldName)

Explicitly mark the parameter instance and field dirty.(Method of javax.jdo.spi.StateInterrogation)