ObjectDB Database Search

is clear I guess. Must add that I am using the Glassfish server 4. I didn't somehow configure JAX-RS

update page http://www.objectdb.com/java/jpa/setting/schema it is not clear how to handle this case

- from the ObjectDB manual - by: "The following operations clear the entire persistence context

.getTransaction().begin(); em.persist(data); em.getTransaction().commit(); em. clear (); TypedQuery q = em

We should add this ability in future ObjectDB versions, thank you for making this point clear

Source) mimac Milan Fabian OK. Apparently the problem is clear now, and we are working on a quick fix

results. I tried em.flush(), em. clear (), etc.. that do not work. Any idea? TIA gzdillon Lai Yang Maybe

subclasses of NamedEntity the field will be initialized as null . support Support Perfect. Thanks for clearing up. btc_es BTC EmbeddedSystems

the EntityManager (L1) cache by invoking clear . JDO provides some additional settings in which objects

part of the codebase from the persist() c) it's not at all clear to me why this shouldn't be idempotent

, similarly to the way that JPA 2.2 streams work. To free memory, however you will have to clear

regards Arne   PS.: maybe I should make clear , that Testclass uses its own equal and hash methods

. Is there a similar option für ObjectDB? If I were unable to make myself clear , here's what I want in

; So to be absolutely clear ... the enhancement takes place around the assignment of a persistent field, not

to pass a non entity object to merge should throw an exception with a clear error message

();         em. clear ();         out.println

you for this report and for the clear test case. Please try build 2.5.4_03, which should fix

described in post #3 clear enough. The other message is because we have referenced the ObjectDB

already made, but they seem to be ignored. So, my (and my company's) wish is to see a clear roadmap of ObjectDB

so starting the next build there will be a clear limit of 64KB. Thank you for this report. To avoid

to remove this restriction. support Support thanks alot your replay makes every thing clear now eng.ahmed ahmed

, with new empty db it works correctly. The objectdb doctor analysis has not found an error. Clearing

",     personID)   .executeUpdate(); em2   .flush(); em2   . clear (); tr

Hello,   My apologies if the answer is already on the website, but I’m struggling to find a definitive answer.  The 10 entity class restriction is very clear , but can each of these classes use unrestricted numbers of embeddable classes?  Do embeddable classes count as

sockets opened idle2_4h_after_GC_trigger - I run jcmd GC.run three times in a row, which cleared

help. Please clear my doubt I know JPA is just a Specification and ORM Frameworks like Hibernate

in the log: index sstsedt cleared then it reports reports about the batches and finally

." Grateful for feedback (although the problem is somewhat academic as a solution is clear ), Webel

Key is separate so i can use indexes, thank you for the documentation on this topic, concise and clear as usual. Thank you support lo Hoel

is clear : SELECT d FROM Department d LEFT JOIN FETCH d.employees WHERE d.deptno = 1 "A fetch join

for every topic and use the issue tracking for clear ObjectDB bugs. Regarding logging - the ordinary

are not completely clear . Please follow the posting instructions and provide a minimal runnable test

is clear . This solution could work with multiple applications only if all the applications always select

, not within some days, for sure. But we need a clear picture/plan when we could have an optimized

to discuss this - issue tracking is only for clear bugs and precisely described feature requests. support Support

;    em . clear ( ) ;          out . println ( em . createQuery

.class); bensteele Ben Steele Maybe it was a cache problem and restarting the database cleared the cache

of embedded objects to collections. Fixed database page objects reuse to release to be cleared

at fault). regards, Darren webel Dr Darren Kelly The problem is clear and understood

(JpaQuery.java:722) ... 15 more This occured when the app tried to clear data for a particular id

version 2.7.4_04 that solves this issue is essential and should remain. It isn't clear

- once it becomes detached existing values are not expected to be cleared but then transparent activation is disabled

(..) call the object is ok. Inside the @PrePersist method all fields are cleared .  mosi0815 Ralph Moser

Remove the entity object, EntityManager is flushed & cleared , Transaction is not committed Count

of database corruption, and in the worst case restarting the system to clear all cached data may help, for now

;     em. clear ();                  entity = em

. clear (); } }); em.getTransaction().commit(); Query q1 = em.createQuery("SELECT count(my) from MyEntity

of that exception? It is clear that you get a NoResultException that you do not expect. A test case

to clear the collection first, commit that and then remove the Contact? thanks! quasado Alexander Adam

it - it could help. In this case the test can be complex since the bad result is very clear . Your last test