About flush

manual

Working with JPA Entity Objects

Explains the entity object lifecycle and the persistence context. Entity objects are in-memory instances of entity classes (persistable user defined classes), which can represent physical objects in the database. Managing an ObjectDB Object Database using JPA requires using entity objects for many oper ...

 
api-jdo

javax.jdo.Transaction

The JDO Transaction interface provides for initiation and completion of transactions under user control.(Interface of JDO)

 
forum_thread

Spring Transactions (@Transactional) within ObjectDB

Hi, We are using OBD with Spring and transactions are managed by Spring. Our spring service interfaces take list of objects and persist them and the interface service is marked as @Transactional. We iterate through the list apply business validations and persist them one by one in a loop. ( Using Spring Data) We have noticed that in a loop 1st object is persisted and then we if lookup the same object we don't get it back on lookup. ... Build 2.5.2_01 adds support for enabling auto flush by default, by setting a system property: System. setProperty ( "objectdb.temp.auto-flush" , "true" ) ; before loading ObjectDB, or as a ...

 
forum_thread

Error using query with MAX() function

I have a class that is persisting a Entity that holds remarks and a time. Then when I query for the latest remark I get a internal error when the remark is larger than 1966 chars. Here is a test class and entity that reproduces the problem on my system. ... If you are using EntityManager 's flush you should try build 2.2.3_04 that fixes a critical bug. ... == 0 ) {   em. flush ( ) ;   em. clear ( ) ...

 
api-jdo

javax.jdo.Query

The Query interface allows applications to obtain persistent instances, values, and aggregate data from the data store.(Interface of JDO)

 
issue

ArrayIndexOutOfBoundsException: -1

I've attached a test which fails with the error "ArrayIndexOutOfBoundsException: -1". It runs 10 threads which create and persist objects. The objects are based on application objects so its not a single class test I'm afraid but it is standalone. I'm running as follows: java -classpath objectdb.jar;test.jar PersistTest I've attached the test jar, a jar containing the source and the odjectdb.conf. ... at com.objectdb.o.OBM.flush(OBM.java:739) ... 1 more Caused by: ... zero size. In some situations (e.g. when using flush that is followed by other operations and then commit) - the page cache ...

 
forum_thread

problem with lazy loading - unittest project attached

hi, i'm still testing objectdb together with spring-data-jpa. i made a test which should simulate 4 requests 1. save entity 2. read an existing entity, add onetomany relation 3. read an existing entity, add another onetomany relation 4. read entity, get relations. i have the feeling this is not the optional way to test this, because of the differnt transaction behavior. the test is not transactional, but the spring repository methods are. ... commit). Using EntityManager 's flush during the transaction. ObjectDB Support ...

 
forum_thread

PersistenceException: Failed to locate field

Hi, have recently been running into this issue when changing the schema: com.objectdb.o._PersistenceException: Failed to locate field in this case, adding a primitive String field to an Entity. pretty sure that in the past schema evolution would not have triggered errors, is this case, a simple new field, shouldn't the policy be to add a null in that field, or other default for that primitive. ... to an old version, shouldn't it automatically flush it's caches if the schema evolves? or at least shouldn't ...

 
issue

Negative snapshot user count exception

I found the following stack trace in my log files; it's cropped up a number of times: Bug Version: 2.5.2 Priority: Normal Status: Fixed Replies: 8 Type:  Bug ...

 
issue

stress test -> com.objectdb.o.InternalException: null

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, but they are relatively light, and the db has just a few MB at the moment. After a few minutes I got this exception. If I decrease the load, it doesn't happen. If I increase it, I get it very often. Any solution/fix? A sample project is very hard, if not impossible, to create, because it uses all the system. ... TestEntity ( ) ) ; em1. flush ( ) ;   EntityManager em2 = ...