ObjectDB Database Search

index: @Index(members={"startDate", "toExtension"}),   We tried clearing the EntityManager cache ... with the the following code (note, em. clear () at the start of the method, where em is an instance of an EntityManager): public List getExtensionByDate() { em. clear (); // TODO Remove me for production. Testing slow query

also load the private interface. Why is this necessary, is not clear to us. Correct way would ObjectDB ... also load the private interface. Why is this necessary, is not clear to us. The ObjectDB type manager ... to avoid as long as it is not necessary. No need. The subject is clear . What would be a good

;      em. clear ();         em.close ... , seems to be well merged   em.getTransaction().commit();   em. clear ();   em.close ... , let's check if children are retrieved   em. clear ();   em.close();   emf.close();  

all the details are clear . Why should you roll back that view transaction, what is the purpose of comitting ... , although not all the details are clear . Why should you roll back that view transaction ... . Rollback is fine, of course, and with your detailed explanations it is clear now why you need

.persist(guest); em.getTransaction().commit(); em.flush(); em.refresh(guest); em. clear (); em.close ... .getTransaction().begin(); em.merge(guest); em.getTransaction().commit(); em.flush(); em. clear (); em.close ... .setParameter(s, map.get(s)); boolean que = q.executeUpdate() 0; em.getTransaction().commit(); em. clear (); em

is needed if used to clear all cache, e.g. to open a new EntityManager after such query operations and disable the L2 data cache. support Support What about calling em.flush(); em. clear ... ; I have done some test cases, and doing a em.flush(); em. clear (); after the query

"XId [a=" + a + ", b=" + b + ", c=" + c + "]"; } } public static void clear (EntityManager em) { Instant t = now(); em. clear (); out.println(" clear \t" + between(t, now()).toString()); } public static void

; at com.objectdb.jpa.EMImpl. clear (EMImpl.java:414) ~[EMImpl.class:na]       ... ;  at com.objectdb.jpa.EMImpl. clear (EMImpl.java:411) ~[EMImpl.class:na]     

layer). If after reading the other thread you have a clear picture of how you think ObjectDB ... , currently this is not automatic. Fill a detailed feature request if you have a clear picture of how you think ObjectDB should handle this. support Support

.objectdb.o.PGC:w: line number 232) is less clear . It points to a synchronized statement. Maybe ... .no-resize- clear , to true - to enforce a quick file resizing.     support Support    

. Specifically: is it advised to use a new EntityManager with every transaction, or to use one, and clear ... a detached entity object (e.g. after clear ). It doesn't seem to be related to the IDE that you use. support

more @OneToOne gives: [ObjectDB 2.4.1_01] javax.persistence.PersistenceException Failed to clear field ... .main(RemoteTestRunner.java:197) Caused by: com.objectdb.o.UserException: Failed to clear field

to clear field property com.contextspace.AddressTest$AbstractContactDetail.type using reflection (error ... .RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: com.objectdb.o.UserException: Failed to clear

:     System.setProperty("objectdb.temp.no-resize- clear ", "true"); Alternatively ... is cleared with zeros. With this settings, the new file space may contain garbage (such as data from

MyApplication If the classes are not enhanced, at least call the clear method of EntityManager ... , so I'm not sure I can call clear on entity manager, anyway thanks for your help. 4410 Arsenii So just

= subject.getPrincipals(); if (principals != null) { principals. clear (); } return false ... logout() throws LoginException { final Set principals = subject.getPrincipals(); principals. clear

Hi! I'm facing a really strange behavior, which I can't yet reproduce, but it happened 3-4 times already. ObjectDB seems to clear some fields that are @ElementCollection Set of my objects ... is unclear. What do you mean by clearing some fields? Please clarify. support Support The field

;  em.getTransaction().commit();         em. clear ();    ... Keskes Thanks for the clear test case that demonstrates the issue. Please try version 2.5.6

.getTransaction().commit();         em. clear ();     ... ;   em.getTransaction().commit();         em. clear

predefined and might be added dynamically), if I didnt explain the problem clear enough please let ... of 'singleton persistent objects' is clear . You wrote: "This is what i can achieve if i have ability

Hi, Is there a way to find the number of managed entities given an entity manager? My application has some memory leaks - I am doing clear () on the entity manager(s) but may be I forgot some ... after clear anyway. Consider producing and checking a heap dump (e.g. using VisualVM). support Support

', but most Values of the Columns are missing. With a  em. clear () inside the Loop, all tables are exported ... classes with reflection you lose that benefit. support Support That's clear - and  I

; /**      * Clear the content of the originalString.      *      * The OriginalValue must be cleared if the value has been changed.  

using an explicit EntityManagerFactory it is not clear to me how to "inject" easily specs ... is the same in both case, but at least the path is clear . Note also that the user and password

;    emg. clear ();         emg.close();    ... ;   emg. clear ();         emg.close();    

of a specific parent? Having a parent with 500K children, when I clear the list by parent.getChildren(). clear (), it loads all children then empties the list and save the change. Is it possible

to stop master, clear all recording files, switch to all mode: Then I stopped also the slave Removed ... again after clearing transaction files which would be unpleasant. However, for replication you only need the last

? After the augment of em. clear (), output changes to 301000 per second. It still below your original InsertTest. gzdillon Lai Yang It seems that your classes were not enhanced (the huge difference when calling clear

statistics. You can see that suddenly on starting some index is cleared (doctor should correctly create ... demonstrate the ~20 seconds in a consistent way? It is just not clear from post #1. support Support

since it is a different topic than the original post. support Support So to be clear ... columns are created

Hi, I've never used an OODB, I'm looking for a starting point but a recurrent concern is the Data Portability one. More clear : what options / strategies do I have to export / move my data to another  tool, if there is a need to? One key point of Ojectdb (as far as I had read) is Code

the configuration , so strong references will be used automatically until the persistence context is cleared

are removed/deleted from the databases - it is the application responsibility to clear any references

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

I've had a quick read through the features/FAQ and haven't been able to find a clear answer. I'm looking at replacing a setup of H2 where I have 40GB in-memory backed by 800GB on-disk, the 40GB in memory represents the first 40GB of the 800GB on-disk for super-fast recent entry searching

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

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

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

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

;  em. clear ();     trans.begin();    }   }   trans.commit

' again of cleared up the issue. As I assign no ID's in my GUI - it seems that there could be a small bug? I'm

= tn2.getTa();   System.out.println(Arrays.toString(la));   em. clear ();     tNode

() and so other builders can access ExtRequestBean request; /** * Use for multi-shot builder to clear ... builder to clear lazy builder method private triggers. */ private void reset() { project = null

. felixobjectdb Richard Szurgot Sorry! - I've double checked the test and it is bad. I'm not clearing ... I can tell is that the problem occurs after I restart the server & test without clearing

().commit();   entityManager. clear ();   parentEntity = entityManager.find(ParentEntity ... ;    em. clear ();         e = em.find(MyEntity.class, 1l

 generic classes is also not supported. ObjectDB should probably produce a clear error message in ... :  ObjectDB should probably produce a clear error message in that case. Yes it should, to help

.getTransaction().commit();         em. clear ();       ... ;      em. clear ();         em.close();   

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

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

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