About find

91-100 of 200Refresh
Issue
1

Internal Exception and Index Problems

Dear Support Team, we have an urgent issue in a productive database. The objectdb doctor finds ... have this problem. Thanks, it solved the issue. It would be great if you could find out how this happened ... userName=...). Even the doctor finds no error which makes it pretty hard to find
Forum
1

Is it possible to remove parent/child entities without refresh?

.find(ParentEntity.class, Long.valueOf(1));   entityManager.getTransaction().begin ... ()); } @Test public void testRemoveVariant2() {   ParentEntity parentEntity = entityManager.find ... .find(ParentEntity.class, Long.valueOf(1));   entityManager.getTransaction().begin
Forum
1

Left join fetch behaviour doesn't retrieve children?

will be needed.   Well ... that's enough for me, i give up. I have spent too many hours to find a test case and if i find it, it will be the third bug about the "join fetch" feature. 3 bugs discovered in few days ... i'm afraid to find more in the future, so let's stop the investigation. I switched
Forum
1

Level 2 cache not hit in @ManyToOne

2 JPA cache is activated and it works ok for find by id (tested by changing data in explorer and reading in my app). Problem 1: find by id on Item it's good, it hits the cache, but not for its field ... each time, even though user 5 has been previously loaded by find by id and its class is @Cacheable
Forum
1

Performance problem

the database. You may find out that by a recursive EAGER fetch you enforce loading of the entire database ... combinations of EAGER / LAZY for these relationships. After finding the problematic relationship you can go ahead and analyze the target class in the same way, recursively, until you find the problematic
Forum
1

persists and update together ?

and this will reduce finding same object again. On jpa :     User obj2 = ...; User usr2 = entityManager.find(User.class,user.getGid()); if(usr2 != null) {     entityManager.refresh(obj2); }     else {         entityManager.persist(obj2);     } We need to first find the object
Issue
1

again merger missing logs + objectdb exception

. Please consider enabling recording. If we cannot find the cause now by analyzing the database ... that generates such an InternalException? We will try to find that query The connection between ... corruption. For this we probably have meanwhile a fix. As regards the query, we'll try to find
Issue
1

log entry and massive performance issues

about), the ObjectNode.nodepath is like '/(EL)ANYNAME/(EX)F', you can find a number of these objects linked to objects ... , it happens with all versions you can find the database on hummingbird-systems.com, login with user ... .nodepath is like '/(EL)ANYNAME/(EX)F', you can find a number of these objects linked to objects
Forum
1

Composite Index error 328

{ final UsrlistEntity usrlistEntity = entityManager.find(UsrlistEntity.class, gid ... persistence.jpa.models.UsrlistEntity (error 328)     at com.objectdb.jpa.EMImpl.find(EMImpl.java:603)     at com.objectdb.jpa.EMImpl.find(EMImpl.java:518)     at persistence.jpa.PersistenceJPALogin.login
Forum
1

"Attempt to lock a non entity object" error

:     Test Stored: Ron After find and first lock: Ron Exception in thread "main" [ObjectDB 2.4.7_15 ... ().setRetainValues(true);         em.getTransaction().begin();         p = em.find(Person.class, 1);         em.lock(p, LockModeType.PESSIMISTIC_WRITE);         System.out.println("After find