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

How to use regular expressions in Criteria Builder

regular expressions in queries, so currently you cannot use regular expressions in JPA criteria API ... out where this would be in the criteria builder. {     CriteriaBuilder cb = emf.getCriteriaBuilder ... an extension, but that extension is limited to string-based JPQL queries, as the criterial API is not


javax.persistence.criteria Interface CriteriaBuilder.SimpleCase<C,R> Superinterfaces: Expression<R>, Selection<R>, TupleElement<R> Interface used to build simple case expressions. Case conditions are evaluated in the order in which they are specified. Since: JPA 2.0 Selection<X> alias(String name


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


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

GROUP BY and HAVING clauses

.currency HAVING COUNT(c) > 1 can be built using the criteria query API as follows: CriteriaQuery ... become inaccessible. GROUP BY and HAVING in Criteria Queries The CriteriaQuery interface provides

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