ObjectDB ObjectDB

Internal Website Search

61-70 of 200 resultsRefresh

IN expression in a Criteria Query

is with Criteria Language. This code: In<Employee> inExpression = cb.in(root.get(Computer ... system, and unfortunately subqueries is one of them. Regarding the criteria query, it is unclear where exactly ... Fabian Regarding the criteria query issue, please provide the complete query string

Criteria Query results in a NoResultException instead of returning object

(); CriteriaQuery criteria = builder.createQuery(identityClass); Root root = criteria.from(identityClass); criteria.select(root); List<Predicate> predicates = new ArrayList<Predicate ... ()));     criteria.where(predicates.toArray(new Predicate[predicates.size()])); return em.createQuery

Threading Problem (maybe with Criteria)

WHERE m_age=50", AdvoluxUID.class); instead of Criteria API CriteriaBuilder cbuilder = manager ... . 100000) the test opens the Database, start some queries with criteria in several threads (maybe 10 ... (ManagedTypeImpl.java:199) at com.objectdb.jpa.criteria.PathImpl.get(PathImpl.java:114) at com.objectdb


javax.persistence.criteria Interface CriteriaBuilder.Coalesce<T> Superinterfaces: Expression<T>, Selection<T>, TupleElement<T> Interface used to build coalesce expressions. A coalesce expression is equivalent to a case expression that returns null if all its arguments evaluate to null


javax.persistence.criteria Interface AbstractQuery<T> Subinterfaces: CriteriaQuery, Subquery The AbstractQuery interface defines functionality that is common to both top-level queries and subqueries. It is not intended to be used directly in query construction. All queries must have: a set of root


javax.persistence.criteria Interface CriteriaBuilder.In<T> Superinterfaces: Expression<Boolean>, Predicate, Selection<Boolean>, TupleElement<Boolean> Interface used to build in predicates. Since: JPA 2.0 Selection<X> alias(String name) Assigns an alias to the selection item. Assigns an alias


javax.persistence.criteria Interface Fetch<Z,X> Superinterfaces: FetchParent<Z,X> Represents a join-fetched association or attribute. Since: JPA 2.0 Fetch<X,Y> fetch(String attributeName) Create a fetch join to the specified attribute using an inner join. Create a fetch join to the specified


javax.persistence.criteria Interface FetchParent<Z,X> Subinterfaces: CollectionJoin, Fetch, From, Join, ListJoin, MapJoin, PluralJoin, Root, SetJoin Represents an element of the from clause which may function as the parent of Fetches. Since: JPA 2.0 Fetch<X,Y> fetch(String attributeName) Create

ArrayIndexOutOfBounds with Critera API and function call

to our customer and went against a show-stopper again. We're building a simple query with the criteria api ... () { return 100; } }; Create Selection Query (Critera-API) from * TestEntity and add WHERE class ... the criteria we get this: 11:20:06,538 ERROR .. Servlet.service() for servlet .. threw exception

Is ObjectDB better than competing object databases?

: ObjectDB is unique in supporting the standard APIs. It is the only object database with built in support for the Java Persistence API (JPA). It also supports a more recent and advanced version of the Java Data Objects (JDO) API than competing object databases. By using a standard API such as JPA

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