About comparison

11-20 of 52Refresh
Result
14

ObjectDB Object Database Features

, AVG, MAX, MIN). Query Expressions Path navigation expressions using the dot (.) operator. Comparison
Manual
14

Index Definition

the need to access the entities themselves. Instead, because of the comparison in the WHERE clause
Manual
14

JPA Criteria API Queries

, substring, ...). Collection expressions (isEmpty, isNotEmpty, isMember, isNotMember, size). Comparison
Manual
14

JPA / JDO Class Enhancer

tracking of persistent field modifications, avoiding the need for snapshot comparison of entities (as
Manual
14

Logical Operators in JPQL and Criteria API

> that represents many operator and function expressions whose type is boolean - such as comparison operators
FAQ
14

Is ObjectDB better than competing object databases?

Naturally, this is not the place to look for an unbiased answer for this question. However, you should consider the following points when doing your own objective comparison of object databases: ObjectDB is unique in supporting the standard APIs. It is the only object database with built in support
JDO Doc
6

setFilter(filter)

, except for these differences: Equality and ordering comparisons between primitives and instances of wrapper classes are valid. Equality and ordering comparisons of Date fields and Date parameters are valid. White
JDO Doc
6

javax.jdo.Query

the Java language, except for these differences: Equality and ordering comparisons between primitives and instances of wrapper classes are valid. Equality and ordering comparisons of Date fields and Date
JPA Doc
4

javax.persistence.OrderBy

the ordering must correspond to columns for which comparison operators are supported. The dot
Forum
3

Object comparation never matches

/query/jpql/comparison Section "Comparable Data Types" Comparison is supported for values ... again. However, there are still reasons to prefer value comparison as suggested in #2 above: Value comparison is compatible with JPA and therefore more portable. Value comparison