13 | JPA Query Expressions (JPQL / Criteria) / Criteria Variables JPQL / Criteria Parameters JPQL / Criteria Literals Every query expression consists |
13 | JPA Queries variables, join and fetch): Other criteria query expressions (for all the query clauses): |
13 | Obtaining a JPA Database Connection variable represents the ObjectDB home directory (by default - the directory in which ObjectDB |
13 | JPA Metamodel API the above sets extend the Bindable interface, which may be used in defining criteria query variables in |
11 | combined index not used:notNull])) <x> v$1:bound(a.objectsInCharge))" eval="4.9675" variable="v$1 ... -07-20->3_3_0:notNull]))" eval="2.9675" variable="a"> <btreePlan plan="index(esst[3_3_0_2018-07-20->3_3_0:notNull])" eval="0.9675" variable |
1 | [ODB1] Chapter 8 - ObjectDB Server are inherited except the name attribute. The $user variable (in the path attribute of $standard |
1 | [ODB1] Chapter 9 - ObjectDB Explorer of the query. Optional JDOQL components, such as filter, parameters, variables, ordering and imports (chapter |
1 | [ODB1] Chapter 5 - JDO Connections this. It is mainly a matter of style whether or not to use a separate variable to hold the Transaction |
1 | addSubquery(sub, variableDeclaration, candidateCollectionExpression, parameters) include the candidate class, filter, parameter declarations, variable declarations, imports, ordering ... of the variable containing the results of the subquery execution. If the same value of variableDeclaration ... variable. If the subquery parameter is null, the variable is unset, effectively making the variable |
0 | setFilter(filter) of the Query; and for all variables there exists a value for which the filter expression evaluates to true ... for the evaluation of the current set of variable values. Other values for variables might still qualify ... (Collection types) is specified using a variable declaration and the Collection.contains(Object o |
