About weak

1-10 of 40Refresh
Manual
102

Entity Management Settings

: weak" level2="0mb" /> The element specifies settings of the two cache mechanisms ... the persistence context of the EntityManager (which serves as a first level cache). The valid values are "weak
Manual
30

Working with JPA Entity Objects

during a transaction are held in the persistence context by weak references. Therefore, when a managed entity ... soft references instead of weak references. The contains method can check if a specified entity
FAQ
21

Is ObjectDB a NoSQL Database?

ObjectDB is a unique NoSQL database. It doesn't have the known disadvantages and limitations of NoSQL technology, which are weak query capabilities and lack of ACID (atomicity, consistency, isolation, durability). Unlike other NoSQL solutions, ObjectDB provides full support of rich complex queries
Issue
8

Best practise loading big data

results="32mb" programs="500" /> Entity Chaches: So level 2 cache is deactivated. References in level 1 cache is weak and we can observe that unreferenced entities ... the unused entities. When reading further, the cache size and the number of weak references still grows
Issue
5

Use temporary files to enable very large transactions

objects instead of very 10,000 entity objects.      When the 2nd ... ref="weak" level2="0" />                           weak references and can be removed by GC. Can you explain this case?   ObjectDB manages about 20
Forum
4

Entity Management Config questions

/setting/entities: The element specifies settings ... ). The valid values are "weak", "soft" and "strong". Modified entities are always held by strong ... : What exactly is the difference between "weak", "soft", and "strong" references? The following blog
Forum
4

Soft Reference Object Cache Recommendation

(unlike weak references). Thank you for your investigation.  I will do more investigating ... ObjectDB to use weak references but then using persistent object callback/listeners to track all objects in ... when it should be freed? Even after using "weak" references, and closing PersistenceManagerFactory
Forum
3

EntityManagerFactory Fails To Swtich Over To Slave When Master Is Unavailable

" reflection="warning" />                                                                
Forum
3

Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01)

weak references, so as soon as you release  your own references to these entity objects ... released, please provide a heap dump. Yes we know about WEAK REFERENCEs in ObjectDb to application entities
Forum
3

PersistenceException: Failed to locate field

" reflection = "warning"/>