ObjectDB ObjectDB

Internal Website Search

1-10 of 42 resultsRefresh

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

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 object

[ODB1] Chapter 6 - Persistent Objects

been modified or deleted during a transaction are held in the cache by weak references

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

Best practise loading big data

: So level 2 cache is deactivated. References in level 1 cache is weak ... size and the number of weak references still grows. One could expect that the could be reused ... just one open transaction. Objects are read so there they are still referenced by weak refernces. GC

Use temporary files to enable very large transactions

entity objects.      When the 2nd level cache is enabled, ObjectDB ... >                                

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? dmoshal David Moshal

Soft Reference Object Cache Recommendation

because this is the way soft references work (unlike weak references). support Support Thank ... suggestions? Perhaps setting ObjectDB to use weak references but then using persistent object ... ObjectDB is not holding on to memory when it should be freed? Even after using "weak" references

500Mb ObjectDb database opening issue

500Mb ObjectDb database opening issue

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

for every persisted object, but uses weak references, so as soon as you release your own references ... ObjectDB objects are not released, please provide a heap dump. support Support Yes we know about WEAK

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support