89 | KEY() / VALUE() not recognized in JPQL??KEY() / VALUE() not recognized in JPQL?? |
17 | JPQL support for mapped by (inverse) collectionsJPQL support for mapped by (inverse) collections |
13 | Is ObjectDB better than competing object databases?, as part of its support of JPQL (JPA Query Language) and JDOQL (JDO Query Language). ObjectDB is faster than other products. |
13 | JPA Named QueriesA named query is a statically defined query with a predefined unchangeable query string. Using named queries instead of dynamic queries may improve code organization by separating the JPQL query strings from the Java code. It also enforces the use of query parameters rather than embedding literals |
13 | What are the main benefits of using ObjectDB? JPQL (JPA Query Language) and JDOQL (JDO Query Language) queries directly, where ORM tools first |
13 | JPA Annotations for SQL QueriesThe following JPA annotations are designated for SQL queries on relational databases: ObjectDB supports only the preferred JPA query language, JPQL, and silently ignores all the above annotations. |
13 | ObjectDB 2.8 Developer's Guide, retrieve, update and delete database objects. Explains how to use the JPA Query Language (JPQL). Presents |
13 | Deleting JPA Entity Objects when many entity objects have to be deleted in one operation. The DELETE Queries in JPA/JPQL in chapter 4 explains how to use JPA DELETE queries. |
13 | Is ObjectDB a NoSQL Database?, using two standard Java query languages: JPQL (Java Persistence Query Language) and JDOQL (JDO |
13 | Criteria Query Selection and Results, since they might be useful also in string based JPQL queries. Using tuples with non criteria queries is supported by |
