Home » Search

About logical

1-10 of 38Refresh
Manual
405

Logical Operators in JPQL and Criteria API

Logical operators in JPQL and in JPA criteria queries enable composition of complex JPQL boolean expressions out of simple JPQL boolean expressions. Logical Operators ObjectDB supports 2 sets of logical operators, as shown in the following table: Set 1 - JPQL / SQL Set 2 - Java / JDO AND && OR
Manual
77

JPA Query Expressions (JPQL / Criteria)

] MEMBER [OF] and the [NOT] LIKE operator. Logical operators: AND, OR, NOT. In addition, JPA queries ... , isMember, isNotMember, size). Comparison expressions (equal, notEqual, gt, ge, lt, le, between, isNull, ...) Logical expressions (and, or, not, isTrue).
Manual
43

Comparison in JPQL and Criteria API

to <>. When at least one of the two operands is NULL, == and != implement the ordinary Java logic, in which, for example, null == null is true. All the other operators implement the SQL logic in which NULL represents an unknown value ... follow the logic of Java's equals, comparing the content rather than the identity. Date values
Manual
27

WHERE clause (JPQL / Criteria API)

, relational operators, logical operators) and functions (numeric functions, string functions, collection ... "), a)     ) ); See the Logical Operators page for explanations on boolean expressions and predicates that can be used in a criteria query WHERE clause.
Manual
19

JPA Criteria API Queries

expressions (equal, notEqual, gt, ge, lt, le, between, isNull, ...) Logical expressions (and, or, not
Manual
19

JPA Persistence Unit

A JPA Persistence Unit is a logical grouping of user defined persistable classes (entity classes, embeddable classes and mapped superclasses) with related settings. Defining a persistence unit is optional when using ObjectDB, but required by JPA. persistence.xml Persistence units are defined in
Result
19

ObjectDB Object Database Features

operators (<, <=, >=, <>, =, !=, ==, BETWEEN, IS NULL). Logical operators (AND, OR, NOT
JDO Doc
5

javax.jdo.InstanceCallbacks

the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0 void
JDO Doc
5

javax.jdo.listener.DeleteCallback

so that fields referenced can be used in the business logic of the method. Since: JDO 2.0
JDO Doc
5

jdoPreDelete()

after this call are disallowed. This method is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0