ObjectDB Database Search

as arguments. Path expressions that navigate from one object to another. Instances of user-defined ... . However, they are more often used in JPQL path expressions that navigate to values of simple types, such as ... by all six comparison operators and used for ordering . Navigation through path expressions A path

;persistent object of class X. Can I  navigate  (as opposed to using JOIN) to  ... Regards geekox86 Mohannad AlAwad Yes, you can navigate from any managed entity object to any ... it to be done in JPA/JDO queries. How about arrays like x.array[1] and x.array[1][2] ? If such navigations

Greetings ObjectDB team, Suppose I pass a List of persistent objects to some query as a parameter, can I navigate to those objects' fields ? E.g.: SELECT x FROM ClassX x WHERE x.a IS MEMBER OF :y.b Thank You ! geekox86 Mohannad AlAwad You cannot navigate from a collection of objects

Hello, I need to evaluate a field ("identifier") which is situated in a collection, within an entity. As stated in the documentation it is not possible to navigate there with the dot operator since its a collection. Is it there a way to evaluate this field? Here is the query, the entity

Pre-detach loading: retrieval by navigation not working in if statement

an automatic query when the entity is retrieved. Note : Navigation through inverse fields is much less efficient than navigation through ordinary persistent fields because it requires running queries ... two unidirectional relationships is usually more efficient, unless navigation in the inverse direction is rare

predicate ├─ Path # Navigation path (attributes) ├─ ParameterExpression # Query parameter ... predicates. A navigation path to an attribute value or a referenced entity. A type-safe representation

, including transparent navigation to other database objects, transparent update detection , support ... of managed entities (for example, transparent navigation and transparent update detection

support for transparent navigation and fetching is convenient because it provides the illusion that all database objects are available in memory for navigation . However, this feature can also cause

operators, listed in order of decreasing precedence: Navigation operator ( . ) Arithmetic operators ... on the following pages: Literals and dates ( literal , nullLiteral , currentDate , …) Paths, navigation

navigation and You can access all persistent fields of an entity freely, regardless of the fetch policy, as ... , the entire object graph is available for navigation , regardless of the fetch policy. The fetch

(no activation depth) - objects are retrieved from the database automatically by navigating  from ... navigation expressions using the dot (.) operator. Comparison operators (

makes navigation easier. Because references between database objects are represented as parent-child relationships, you can navigate between objects by expanding nodes, similar to exploring objects in

navigation from detached objects is not supported. You can only access persistent fields

String values can appear in JPQL queries in several forms: As string literals , for example, 'abc' and '' . As parameters when string values are passed as query arguments. As path expressions that navigate to persistent string fields. As the results of predefined JPQL string manipulation functions

Date and time expressions can appear in JPQL queries in the following ways: As date and time literals --for example, {d '2011-12-31'} and {t '23:59:59'} . As parameters --when date and time values are passed as arguments. As path expressions --to navigate to persistent date and time fields. As

Collections can appear in JPQL queries in the following ways: As parameters when a collection is passed as an argument. As path expressions when navigating to a persistent collection field. IS [NOT] EMPTY The IS [NOT] EMPTY operator checks whether a specified collection is empty. For example: c

Numeric values can appear in JPQL queries in several forms: As numeric literals , such as 123 and -12.5 . As parameters that are bound to numeric arguments. As path expressions that navigate to persistent numeric fields. As aggregate expressions , such as COUNT . As collection functions

query expressions: Literals and dates ( literal , nullLiteral , currentDate , ...) Paths, navigation

The Jakarta Persistence Criteria API uses a specific set of interfaces to construct the FROM clause of a query. These interfaces define query variables, including entity roots and various join types, to manage data navigation and retrieval optimization. The interface hierarchy for the FROM clause

A main limitation of detached objects (as explained on the Detached Entities manual page) is: Retrieval by navigation from detached objects is not supported, so only persistent fields ... for that) but for us the inability to navigate lazy relationships of detached entities is a big showstopper, as we rely

is invalid. You cannot navigate through collections in JPQL directly. You have to use JOIN to define ... Support of direct navigation from collections (with no JOIN) was just added in build 2.2.4_02 ... to JPQL using a hint the following exception is thrown on attempt to use the new navigation from

in the [ Navigator ] window and selecting Report Run Report :  

project: Right click the Reports node in the [ Navigator ] and select New Report . Enter the report

; Then one can navigate to Classes, double click "byte[]" to view its instances, click "Compute retained sizes ... , one can navigate the selected JdoBlob2 object's reference listing in JavaVisualVm to discover which object(s ... ; Using the heap dump I navigate through a lot of unrecognizable stuff under there (all presumably

be aware that navigation from the mapped by (inverse) side to the owner side is slower ... ;relationships (with no mapped by). You will have to maintain both sides, but navigation may be faster since no queries will be required. This ability (of navigation in the to many direction with no queries

/entity/fields#Inverse_Fields . A query will still be executed (i.e. navigation from Customer to Order ... above, which is less efficient in ORM-based implementation and requires a JOIN table and a query for navigation ... Moshal It depends on what your application does, of course. But assuming that navigation

.PersistenceException Navigation from 'java.util.Calendar' through 'DAY_OF_WEEK' is invalid (error 763) at com ... .run(EventDispatchThread.java:91) Caused by: com.objectdb.o.UserException: Navigation from 'java.util

Hi, I have a strange problem, There was an exception while trying to navigate to 'Drivers' with the root cause 'java.lang.NullPointerException: Cannot invoke "com.objectdb.o.MMM.t ... . This is the stack trace (i can send by email more info) There was an exception while trying to navigate

First, the new Explorer in ObjectDB is fantastic! This is exactly what we've needed - an easy way to do ad-hoc JPQL queries and navigate through the results and even make small changes to primitive ... that are opened while navigating the results. My initial result might have only a few records

expression in JPQL because  messageList is a List and navigation from a list must be done by an additional variable. ObjectDB supports navigation from lists as an extension, so the following query

and then navigate to each element separately, each navigation requires a separate round trip

I am having trouble with the Explorer.  I can open the db just fine. I can open a few simple extents and view/ navigate fine also.  The problem occurs when I view the more complex extents. The Explorer will not repaint the right pane.  I drag off screen to force repaint and get(right

find and by navigation (and not in queries). You may try the following undocumented ObjectDB query

as a pair of (type + id) rather than just an id. This enables faster navigation between objects, as

baURI is a byte[]; JP QL select e.baURI.length from URI e where id=82778 JP QL [ObjectDB 2.2.9_04] javax.persistence.PersistenceException Navigation from 'byte[]' through 'length' is invalid (error 763) at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:636) at util.JPQLcmd.QureyCMD(JPQLcmd

? Yes. They are useful when the query includes navigation between entities (directly or using JOIN).   support Support

of objectC, and I cant find any reason for that. Could be any bug in ObjectDB when I retrieve by navigation

it on Amazon's VPS, then unzip the ObjectDB archive, then you navigate into "bin" folder of the folder

OR o.id = :userId Notice that the navigation   root.get("owner").get("id") is implemented as

" is considered as a string literal value rather than as a navigation expression), and because this constant

The associated feature request is:  Navigation through lazy loading from Detached Objects   webel Dr Darren Kelly

the A instance with no another because navigation through a relationship is implemented using JOIN (i.e

of is now provided under forum posting: Pre-detach loading: retrieval by navigation not working in

the rest are just ORs, no?? Alex quasado Alexander Adam 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

navigation through a broken reference (probably a reference to a deleted object) during query execution

Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running

Added support of navigation through collections  (as a JPQL extension). Added version display to the Server and Explorer About dialog boxes. Fixed an UPDATE/DELETE query bug in client-server mode. Fixed an ArrayIndexOutOfBoundsException in retrieval of large objects. Fixed Explorer display

I have a problem loading lazy associations by access/ navigation with an @Embedded attribute containing an @ElementCollection which is lazy loaded.  I'm not sure if the same problem exists elsewhere.  Furthermore, if I set a breakpoint in the right spot in debug mode, everything works

the quotes I've found confirming that EclipseLink permits navigation of lazy loaded relationships