Home » Search

About comparison

11-20 of 52Refresh
Manual
24

Query Parameters in JPA

the above example, a comparison of :name to a field whose type is String indicates that the type ... part of the newly constructed java.util.Date instance is discarded. This is very useful in comparison
Manual
17

Index Definition

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

JPA Criteria API Queries

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

Logical Operators in JPQL and Criteria API

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

JPA / JDO Class Enhancer

tracking of persistent field modifications, avoiding the need for snapshot comparison of entities (as
Result
17

ObjectDB Object Database Features

, AVG, MAX, MIN). Query Expressions Path navigation expressions using the dot (.) operator. Comparison
JDO Doc
7

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
7

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
5

javax.persistence.OrderBy

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

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