ObjectDB Database Search

;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

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 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

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

; 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

.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

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

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