ObjectDB Database Search

51-61 of 61 results

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

; Another user might try to navigate and enter "My drawer/Myfolder/someTab/documenta", and I want

Query vs Extent for retrieving data

. The ability to navigate through persistent references transparently, loading necessary objects

Optimization of Map Queries

users, but mainly for storage and retrieval or navigation , and rarely in queries. Actually support

ObjectDB without javax.persistence

:205) at com.btc.ep.base.ui. navigator .ProfileNavigator.refresh(ProfileNavigator.java:160) at sun

Unexpected Exception during commit

me bi-directional navigation of my entities, even though I am only managing a reference

[Explorer] Executing Queries

The new Explorer of ObjectDB 2 supports retrieval of database objects by classes and navigation . Retrieval of database objects by executing queries visually should also be supported. This is one of the features that have been supported by the old Explorer of ObjectDB 1. It has been temporarily

ObjectDB 2.3.7

Fixed a critical issue that may cause database corruption ( issue #630 ). Initial attempt to enable navigation through lazy loading from detached objects ( feature request #326 ). Improved  toString of criteria queries to use aliases ( issue #12 7). Fixed automatic variable naming in criteria

ObjectDB 2.4.0

queries. Fixed a possibly very slow query execution when using entity parameters. Fixed issues in navigation through detached objects .

JPQL support for mapped by (inverse) collections

As discussed and demonstrated in this forum thread , collection operators and methods (IS EMPTY, SIZE, MEMBER OF, IN) are currently not supported for mapped by (inverse) collections. These operations are supported for direct (not mapped by) collections. Navigation and JOIN is supported

Issue with DISTINCT Select

a result of path navigation (e.g. x.a.b ). Only explicit variables are shown in toString

OutOfMemoryError in a query with many variables

doesn't handle well queries with a lot of variables, and complex navigation (e.g.  $1.postalAddresses