Home » Search

About navigation

21-30 of 71Refresh
Manual
15

Strings in JPQL and Criteria Queries

String values may appear in JPQL queries in various forms: as string literals - e.g. 'abc', ''. as parameters - when string values are assigned as arguments. as path expressions - in navigation to persistent string fields. as results of predefined JPQL string manipulation functions. LIKE - String
Tutorial
15

Step 6: Design a BIRT Report Table

to see the table with the real data: You can run the report by right clicking the report node in the [Navigator] window and selecting Report > Run Report:  
JDO Doc
9

javax.jdo.Query

. Navigation through a null-valued field, which would throw NullPointerException, is treated as ... for variables might still qualify the candidate instance for inclusion in the result set. Navigation ... . Navigation through single-valued fields is specified by the Java language syntax of field_name
JDO Doc
8

setFilter(filter)

to support non-mutating method calls as non-standard extensions. Navigation through a null-valued ... might still qualify the candidate instance for inclusion in the result set. Navigation through multi-valued fields ... , this is a reserved word which means the element of the collection being evaluated. Navigation through single
JDO Doc
4

setOrdering(ordering)

must be declared in the candidate class or must be a navigation expression starting with a field in the candidate
Issue
4

Unexpected Query Token / Casting in Query

;) thanks!! Alex I fixed some issue in ObjectDB in navigation after casting. Then I had to add ... on navigation to routingNumber. Another casting will not help here because bankAccounts is a collection, and you cannot navigate from a collection in JPA without introducing a variable (ObjectDB does
Forum
3

how to query by properties of onetomany relations? (Error 990)

. However, this query is invalid. You cannot navigate through collections in JPQL directly. You have to use ... navigation from collections (with no JOIN) was just added in build 2.2.4_02. The following program ... the following exception is thrown on attempt to use the new navigation from collection syntax
Issue
2

Different behavior for two equal queries

execution be finished as the rest are just ORs, no?? Alex Maybe this is the result of navigation through null in one of the OR components. Navigation should be compiled as LEFT OUTER JOIN to avoid losing ... component that causes this query execution failure? Does it have navigation through null
Forum
2

find() cost unreasonable time!

are inefficient for navigation in the inverse direction. ObjectDB supports bidirectional relationships because this is part of JPA. But navigation in the inverse direction from the owned to the owner ... navigation is also expected to be faster than find since entities are retrieved in bulk. gzdillon
Forum
2

JPA vs JDO - which is more efficient for OneToMany queries?

. A query will still be executed (i.e. navigation from Customer to Order will run an automatic query ... implementation and requires a JOIN table and a query for navigation, is implemented differently in ObjectDB ... . But assuming that navigation is mostly from the customer to the orders, when using ObjectDB a collection