ObjectDB ObjectDB

Internal Website Search

41-50 of 172 resultsRefresh

Index causes increased memory usage

with us with understanding what is going on behind the scenes inside object db. When you refer to having "30 open databases", are you talking about having 30 PersistanceManagers open? Or 30 PersistanceManagerFactories? Or ... Dev Team > When you refer to having "30 open databases", are you talking about having 30

Java 9 support

dependencies are allowed without me having to know what is really required by what. You can see that my tool and approach is designed for "just me" to get true Java 9 without having to wait on third parties but at the sacrifice of having everything exposed (which is fine because I am the only one using

OEM license, enhancer

with the system which was created before having the OEM license and before adding enhancer to our maven ... is the same and it is not affected by having or not having a license. support Support

How Should I Configure objectdb.conf to Obtain 256KB Disk IO Requests and Maximize Shared PersistenceManager Entity Cache?

above) appropriate to achieve this goal? CBE CBE Having larger database pages may have other effects ... on an Amazon EBS disk which has max performance at that size and reduces monetary fees by having ... performance at that size and reduces monetary fees by having fewer accesses). So a page size of 256K

Object DB vs EclipseLink/TopLink: Unloaded relationships in detached entities

or the entity manager factory after having detached the entity, the detached entity finds ... is to make the irreducible basic elements as simple and as few as possible without having to surrender ... .” webel Dr Darren Kelly Having remarked on the ObjectDB JavaEE tutorials being too simple, it is worth

find repeated records by JPQL

(select id from TTT s group id having count(id)>1) I dont know how to do this using JPQL, but I use ... #1 contains GROUP BY / HAVING. The outer query in #1 contains the IN operator. The query in #3 ... since in #3 there is no GROUP BY / HAVING. support Support

Is there a way to set EAGER fetch on all "ToMany" collection relationships

Given that the default seems to be FetchType.LAZY for all collections @OneToMany and @ManyToMany. Such as a configuration option. Instead of having to explicitly set fetch in annotation code in every relationship. webel Dr Darren Kelly No. There is no such configuration option, since having EAGER

IN expression in a Criteria Query

: SELECT a FROM Account a GROUP BY a.code HAVING COUNT(a) < 2 It throws following exception: com ... Account a GROUP BY a.code HAVING COUNT(a) < 2 This is an invalid query. In a grouping query

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

of my time. Please attend to this as soon as possible and fix this carefully. I look forward to having this fixed and to having a robust ObjectDB working on my problem, as I am greatly encouraged by ... having performed a query in an EJB and having returned that from a JSF backing bean getter

NullPointerException on initial database creation

Support I'm having trouble creating a simple test case that reproduces it. At this point, I think it may be related to having a class annotated with @Startup or @ApplicationScoped that references

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