Internal Website Search

41-50 of 174 resultsRefresh

Index causes increased memory usage

> When you refer to having "30 open databases", are you talking about having 30 PersistanceManagers open?  ... > > When you refer to having "30 open databases", are you talking about having 30

Java 9 support

sure that inter-module dependencies are allowed without me having to know what is really required by ... without having to wait on third parties but at the sacrifice of having everything exposed ... the meantime, I am reaping the Java 9 benefits without having to wait for all third parties

OEM license, enhancer

to ship a standard database with the system which was created before having the OEM license and before ... 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?

this goal?   CBE CBE Having larger database pages may have other effects ... which has max performance at that size and reduces monetary fees by having fewer accesses). having fewer accesses). So a page size of 256K may work for you. But you may want

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

the entity manager or the entity manager factory after having detached the entity, the detached entity ... the irreducible basic elements as simple and as few as possible without having to surrender ... .”   webel Dr Darren Kelly Having remarked

find repeated records by JPQL

="pre-query"> Select * from TTT t where id in (select id from TTT s group id having count(id)>1 ... contains GROUP BY / HAVING. The outer query in #1 contains the IN operator. 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 ... > No. There is no such configuration option, since having EAGER as the fetch type

IN expression in a Criteria Query

class="pre-query"> SELECT a FROM Account a GROUP BY a.code HAVING COUNT(a) < 2 It throws ... the GROUP BY query: SELECT a FROM Account a GROUP BY a.code HAVING COUNT

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

forward to having this fixed and to having a robust ObjectDB working on my problem, as I am greatly ... my code or using a better example than Guest, the magic moment when a JSF developer having performed a query in an EJB and having returned that from a JSF backing bean getter is supposed to "reattach", or

NullPointerException on initial database creation

the exception? support 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