89 | Duplicate Entity class names causes Exception in Query .... @Entity @NamedQueries({ @NamedQuery(name = "objdbTest.Singleton.getItem", query = "SELECT o FROM Item o WHERE o.cachedKey = :cachedKey"), @NamedQuery(name = "objdbTest.Singleton.count", query ... (name = "objdbTest.Singleton.count", query = "SELECT COUNT(x) FROM objdbTest.Item x") everything works |
86 | Is named-query supported in orm.xmlI prefer to keep custom JPQL named queries in an external file, e.g. orm.xml, rather than in the entity classes, for example: <named-query name= "DataValue.deleteByCapabilityAndCreationtime ... and d.creationtime <= :creationtime </query> </named-query |
19 | Database Management Settings" synchronized="false" /> <index-update enabled="true" priority="40" /> <query-cache results ... by ObjectDB when the database is closed. The name of the recovery file is based on the name ... " operations (which modify the database) have to be recorded. For debugging of query failure |
19 | Database Explorer to view data in ObjectDB databases, execute JPQL and JDOQL queries and edit the content of databases ... the database and their persistent fields and indexes. The [Query] window enables running JPQL and JDOQL queries, as discussed below. Closing a Database Connection Use the File > Close menu command |
18 | JPA Entity Fields the database, but is still available after retrieval by a special automatic query. Note: Navigation ... , since it requires running queries. Inverse fields are essential for collection fields when using ORM JPA ... relationship: @Entity public class Employee { String name; @ManyToOne Department department |
18 | JPA Persistable Types, package or private) and it can be either concrete or abstract. Entity Class Names Entity classes are represented in queries by entity names. By default, the entity name is the unqualified name of the entity class (i.e. the short class name excluding the package name). A different entity name |
15 | Named Query Exception. This could indicate an attempt to create a query using a closed EntityManager. If this is the case, a better error |
15 | Database Connection using JPA for Query instances, which are needed for executing queries on the database. Every JPA implementation ... the database file. Connection URL The createEntityManagerFactory method takes as an argument a name ... .objectdb is considered by ObjectDB to be a database URL rather than as a persistence unit name. To use |
1 | javax.jdo.JDOEntityManager: IllegalArgumentException - if not an entity Since: JPA 1.0 Query createNamedQuery(String name) Create an instance of Query for executing a named query (in the Java Persistence query language or in native SQL). Create an instance of Query for executing a named query (in the Java Persistence query language or in |
1 | getPersistenceManagerFactory(overrides, name, resourceLoader, pmfLoader) overrides, String name, ClassLoader resourceLoader, ClassLoader pmfLoader ) Returns a PersistenceManagerFactory configured based on the properties stored in the resource at name, or, if not found, returns a PersistenceManagerFactory with the given name or, if not found, returns a javax.persistence |
