18 | Is ObjectDB better than competing object databases?Naturally, this is not the place to look for an unbiased answer for this question. However, you should consider the following points when doing your own objective comparison of object databases: ObjectDB is unique in supporting the standard APIs. It is the only object database with built in support |
18 | Logical Operators in JPQL and Criteria API> that represents many operator and function expressions whose type is boolean - such as comparison operators |
18 | Index Definition the WHERE and ORDER BY clauses) saving the need to access the entities themselves. Instead, because of the comparison |
18 | JPA / JDO Class Enhancer tracking of persistent field modifications, avoiding the need for snapshot comparison of entities (as |
18 | ObjectDB Object Database Features. Comparison operators (<, <=, >=, <>, =, !=, ==, BETWEEN, IS NULL). Logical operators (AND, OR, NOT |
18 | JPA Criteria API Queries, ...). Collection expressions (isEmpty, isNotEmpty, isMember, isNotMember, size). Comparison |
5 | javax.persistence.OrderBy the ordering must correspond to columns for which comparison operators are supported. The dot |
1 | [ODB1] Chapter 4 - JDO Metadata objects for every value in the indexed field. Both equality (==, !=) and comparison |
0 | javax.jdo.Query the Java language, except for these differences: Equality and ordering comparisons between primitives and instances of wrapper classes are valid. Equality and ordering comparisons of Date fields and Date |
0 | setFilter(filter), except for these differences: Equality and ordering comparisons between primitives and instances of wrapper classes are valid. Equality and ordering comparisons of Date fields and Date parameters are valid. White |
