About users



Specifies the table that is used for the mapping of collections of basic or embeddable types.(Annotation of JPA)


ObjectDB License

ObjectDB Purchase and License info page.... runtime bundled in a product to unlimited number of end users. For a quote please contact ObjectDB Sales ...


Comparison in JPQL and Criteria API

Explains how comparison operators can be used in JPQL queries, including in comparing null values. Most JPQL queries use at least one comparison operator in their WHERE clause. This page covers the following topics: Comparison Operators Comparing NULL values IS [NOT] NULL Comp ...


JPQL support for mapped by (inverse) collections

As discussed and demonstrated in this forum thread, collection methods (IS EMPTY, SIZE, MEMBER OF, IN) are not supported for mapped by (inverse) collections.   JPA Feature Version: 2.3.7 Priority: Normal Status: Active Replies: 0 Type:  JPA Feature ...


Null enums and IS (NOT) NULL: NullPointerException

Hello. I'm getting NullPointerException when adding %enum field% IS (NOT) NULL or == (!=) NULL in WHERE clause. The same exception using CriteriaQuery. #1 2014-05-01 23:25 Hello. I'm getting NullPointerException when adding %enum field% IS (NOT) NULL or == (!=) NULL in WHE ...


Allow removal of entity class from ObjectDB & Explorer

Hi. It would be very useful to be able to delete an entire entity class from ObjectDB, but especially from Explorer. This is very useful for everyone, but also for clients that don't own a license, thus they're limited to 10 entities / db. During the life time of a software, many changes appear to its data structure. When an entity class becomes unnecessary, we should be able to remove it, thus to get space for another one. Feature Request Version: 2.5.2 Priority: High Status: Active Replies: 0 Type:  Feature Request ...


JPQL Subqueries (JPA 1.0)

The JPQL (Java Persistence Query Language) supports defining subqueries, which are nested queries that are embedded in other queries. Subqueries are currently not supported by ObjectDB, and as a workaround, you can use a sequence of two or more queries, where the results of one query serves as a parameter in the next queries. JPA Feature Version: Priority: Low Status: Active Replies: 0 Type:  JPA Feature ...



Defines a primary key generator that may be referenced by name when a generator element is specified for the GeneratedValue annotation.(Annotation of JPA)


@FetchGroup in JPA similar to JDO

I was checking what's new in different JPA implementation on the market and found quite interesting two features. First of those features is described in this ticket. It's similar to FetchGroup from JDO. It works like this. First you specify attributes to fetch from database: Feature Request Version: Priority: Normal Status: Active Replies: 0 Type:  Feature Request ...



Specifies the primary table for the annotated entity.(Annotation of JPA)