ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
3

JPA Queries

variables, join and fetch): Other criteria query expressions (for all the query clauses):
3

JPA / JDO Class Enhancer

"*.class" The "*.class" expression above is enclosed in quotes to prevent extraction by the shell
3

Eclipse Distribution License - v 1.0

HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
3

ObjectDB Website - Terms and Conditions of Use

Software's web site are provided "as is". ObjectDB Software makes no warranties, expressed or implied
3

Chapter 4 - JPA Queries (JPQL / Criteria)

BY, HAVING, ORDER BY): Then the expressions that are used for building JPQL and criteria query
3

Issue with DISTINCT Select

It is getting more and more frustrating :( We've introduced distinct select instead of regular ... expression '$3' for distinct results at com.objectdb.o.MSG.d(MSG.java:61) at com.objectdb.o.QNF.l ... expressions is a common error (not only in ObjectDB and also in SQL), since there are strict rules
2

substring(x, from, len)

Method javax.persistence.criteria.CriteriaBuilder Expression<T> substring( Expression<T> x, Expression<T> from, Expression<T> len ) Create an expression for substring extraction. Extracts a substring ... expression from - start position expression len - length expression Returns: expression corresponding to substring extraction Since: JPA 2.0
0

[ODB1] Chapter 3 - Persistent Classes

(the "*.class" expression is in quote marks here to avoid auto resolving at the shell level in some
0

[ODB1] Chapter 5 - JDO Connections

, the call to getClass() should be replaced by some other expression (e.g. MyClass.class) in a static context (i.e
0

setResultClass(cls)

of one expression, the result class defaults to the type of that expression. If the result consists of more than one expression, the result class defaults to Object[]. The result class ... . If there are multiple result expressions, the result class must be able to hold all elements of the result

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