ObjectDB ObjectDB

Internal Website Search

31-40 of 46 resultsRefresh

Should I use ObjectDB and JDO?

it might be faster than JPA... ObjectDB has the same speed whether you use JPA or JDO. > I don't

Missing (null) elements in eager loaded references

that, my only option is to try enhancing the classes to speed it up. Thanks for the help so far, I will get back in

Slow searching with two indexes

to (say) 10 results. Is there any obvious way to speed up this querying? Taking minutes is not

Query perfromance problem

perfectly well. The difference in speed is really huge. Thanks for the fix. lwalkowski Lukasz Walkowski

Performance tuning, best practices

is at maximum 30% of activity under heavy load but database queries are let's say not at the speed

Compress ODB file with XML content

, because is it is designed for speed and not for minimum storage space, but compression ratio of 1:50 does look extreme

ObjectDB's Database Doctor Incorrect Error Report

too much about the speed and I/O operations. For sure, it will not make your application 4 times

Merge of entity classes with "mapped by" very slow

it with the new build. support Support Thanks for new build. Fix is working correctly. The speed boost

Bidirectional OneToMany is slow on updated items

the javaagent (which you can see in the contained eclipse launch configuration) Is there any way to speed

Use temporary files to enable very large transactions

which this data is written to a temporary file. Even without speed optimizations, but with priority

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