ObjectDB Database Search
1-41 of 41 resultsJPA Named Queries rather than embedding literals dynamically into the query string and results in more efficient queries. @ NamedQuery and @ NamedQueries Annotations The following @ NamedQuery annotation defines a query ... : @ NamedQuery ( name ="Country.findAll", query ="SELECT c FROM Country c") The @ NamedQuery annotation | |
AnnotationRef jakarta.persistence.NamedQueries JPA Annotation NamedQueries Target: TYPE Implemented Interfaces: Annotation Declares multiple ... . The NamedQueries annotation can be applied to an entity or mapped superclass. See Also: NamedQuery Since: JPA 1.0 The JPA Named Queries article explains how to use NamedQueries . Public Annotation | |
AnnotationAttrRef jakarta.persistence.NamedQueries.value JPA Annotation Attribute in jakarta.persistence. NamedQueries NamedQuery [] value default null (Required) An array of NamedQuery annotations. Since: JPA 1.0 | |
AnnotationRef jakarta.persistence.NamedQuery JPA Annotation NamedQuery Target: TYPE Implemented Interfaces: Annotation Declares a named query ... of the definition of a named query written in the Jakarta Persistence query language: @ NamedQuery ( name = " ... article explains how to use NamedQuery . Public Annotation Attributes QueryHint [] hints default | |
AnnotationAttrRef jakarta.persistence.NamedQuery.hints JPA Annotation Attribute in jakarta.persistence. NamedQuery QueryHint [] hints default {} (Optional) Query properties and hints. May include vendor-specific query hints. Since: JPA 1.0 | |
AnnotationAttrRef jakarta.persistence.NamedQuery.lockMode JPA Annotation Attribute in jakarta.persistence. NamedQuery LockModeType lockMode default LockModeType.NONE (Optional) The lock mode type to use in query execution. If a lockMode other than LockModeType.NONE is specified, the query must be executed in a transaction and the persistence context joined to the transaction. Since: JPA 2.0 | |
AnnotationAttrRef jakarta.persistence.NamedQuery.query JPA Annotation Attribute in jakarta.persistence. NamedQuery String query default null (Required) The query string in the Jakarta Persistence query language. Since: JPA 1.0 | |
AnnotationAttrRef jakarta.persistence.NamedQuery.name JPA Annotation Attribute in jakarta.persistence. NamedQuery String name default null (Required) The name used to identify the query in calls to EntityManager.createNamedQuery . Since: JPA 1.0 | |
AnnotationAttrRef jakarta.persistence.NamedQuery.resultClass JPA Annotation Attribute in jakarta.persistence. NamedQuery Class resultClass default void.class (Optional) The class of each query result. The result class may be overridden by explicitly passing a class object to (String, Class) . If the result class of a named query is not specified | |
Using Enum type in NamedQuery: Field is not found in type in the following JPA Named Query @ NamedQuery (name = "TestQuery",   | |
can not use spring-data-jpa repository with NamedQuery in spring-data-jpa named queries are used to implement repository interface methods, see http://static.springsource.org/spring-data/data-jpa/docs/current/reference/html/#jpa.query-methods.named-queries for example @ NamedQuery (name = "Foo.findByBar", query = "select f from Foo f where :bar member | |
JPA Query API also provides a way for building static queries, as named queries , using the @ NamedQuery and @ NamedQueries annotations. It is considered to be a good practice in JPA to prefer named queries | |
Setting and Tuning of JPA Queries", 6000); For a named query definition - using the hints element: @ NamedQuery ( name ="Country | |
ObjectDB Object Database Features Criteria Query API . Static definition ( named queries ) in annotations (@ NamedQuery ) and XML. Query | |
JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception. NamedQuery ; import javax.persistence. NamedQueries ; import javax.ejb.TransactionAttribute; import javax.ejb ... .TransactionManagementType; @ NamedQueries ( { @ NamedQuery ( name="Guest ... ( "ManagedType Guest not found" ); // NamedQuery does not work // TypedQuery query | |
Problem with entities detection.persistence.Id; import javax.persistence. NamedQueries ; import javax.persistence. NamedQuery ; import javax ... ") @XmlRootElement @ NamedQueries ({ @ NamedQuery (name = "Alumno_odb.findAll", query = "SELECT a FROM Alumno a") , @ NamedQuery (name = "Alumno_odb.findByDni", query = "SELECT a FROM Alumno a WHERE a.dni = :dni | |
openejb jpa jaas module.getPrincipals(); final int id = info.getId(); final TypedQuery namedQuery = entityManager.createNamedQuery("UserPrincipal.findAll", UserPrincipal.class); List resultList = namedQuery .getResultList ... ) @ NamedQueries ({ @ NamedQuery (name = "UserInfo.setClientSettings",query = "update UserInfo ui set ui | |
Duplicate Entity class names causes Exception in Query, only one of them is mentioned in the persistence.xml. I a NamedQuery I use the unqualified class name ... the query on objdbTest.Item package objdbTest; import .... @Entity @ NamedQueries ({ @ NamedQuery ... "), @ NamedQuery (name = "objdbTest.Singleton.count", query = "SELECT COUNT(x) FROM Item x") }) public | |
New to Product & Having An Issue) @ NamedQueries ({ @ NamedQuery (name="Department.findAll", query="SELECT d FROM Department AS d"), @ NamedQuery (name="Department.byName", query="SELECT d from Department AS d WHERE d.name = :name"), @ NamedQuery (name="Department.findByCmpPK", query="SELECT d FROM test.Domain.Department AS d " + "WHERE d | |
Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne).persistence.FlushModeType; import javax.persistence.Id; import javax.persistence. NamedQueries ; import javax.persistence. NamedQuery ; import javax.persistence.Query; import javax.persistence.Version; import uk.co.his.experiment8.common.TestException; @Entity @ NamedQueries ({ @ NamedQuery (name | |
ObectDb 2.3.6 in OSGi environment.class); the corresponding POJO: @Entity @ NamedQueries ({ @ NamedQuery (name = "RuleValueNode.findRoot", query = "SELECT rvn FROM RuleValueNode rvn where rvn.parent is null"), @ NamedQuery ... = true and rvn.parent = :parent"), @ NamedQuery (name = "RuleValueNode.findStandardNodes", query | |
Should derived fields of an EmbeddedId be manually maintained by app code?.persistence.FlushModeType; import javax.persistence.Id; import javax.persistence. NamedQueries ; import javax.persistence. NamedQuery ; import javax.persistence.Query; import javax.persistence.Version; import uk.co.his.test.TestException; @Entity @ NamedQueries ({ @ NamedQuery (name = "numberOfMapItems", query | |
Database Inconsistency or corruption_01") @javax.persistence. NamedQueries ({ /* queries */ }) public class ObjectValue implements metamodel ... .persistence.Table(name="Attributes", schema="dex_01") @javax.persistence. NamedQueries ({ /*  ... .persistence.InheritanceType.JOINED) @javax.persistence. NamedQueries ({ /* queries | |
InterfaceRef jakarta.persistence.TypedQueryReference JPA Interface TypedQueryReference Type Parameters: - an upper bound on the result type of the query A reference to a named query declared via the NamedQuery or NamedNativeQuery annotations ... of all hints specified via NamedQuery .hints or NamedNativeQuery.hints . Since: JPA 3.2 String getName | |
InterfaceRef jakarta.persistence.EntityManager See Also: NamedQuery NamedNativeQuery Since: JPA 1.0 TypedQuery createNamedQuery (String name ... to the specified type See Also: EntityManagerFactory.getNamedQueries NamedQuery NamedNativeQuery | |
Embedded List Why does this NamedQuery only work sometimes? @ NamedQuery (name = "ItemDB.getPartial", query = "SELECT i FROM com.model.ItemDB i JOIN i.lstSupplier s WHERE s.strSupNumber LIKE ?1") I use this to access it. TypedQuery tqItem = emf.createEntityManager().createNamedQuery("ItemDB.getPart", ItemDB.class | |
JPQL query to get entities that does not have a child entity in their child entities for Job and Status with NamedQueries on Job entity and using TomEE for deployment. I am using following queries. FINISHED Jobs between a time interval: @ NamedQuery ( name | |
Cast exception?(); Where the query is a NamedQuery store in Player class file: @ NamedQuery (name="Player.getPlayer | |
Query can't see recently persisted object consistency of objects persisted within the same container transaction? @ NamedQueries ( { @ NamedQuery | |
Composite Index error 328; import java.util.Objects; @Entity @Table(name = "usrlist", schema = "posts") @ NamedQueries ( { @ NamedQuery (name = "UsrListEntity.clearAllIds" , query = "UPDATE UsrlistEntity usrlist SET usrlist.dyId | |
Modifying something with Explorer -> app JPQL with Enum doesn't work anymore with field "type" GOOD found by the the NamedQuery does not correspond with the actual data present ... and click on run button. That's it. Anyway...it's just a NamedQuery that is executed by an EntityManager | |
Trouble bug on explorer. */ @ NamedQueries ({ @ NamedQuery (name = "User.findAll", query = "Select c from User c | |
Object comparation never matches number; Which is a part of Customer object: @MappedSuperclass @ NamedQueries ({ @ NamedQuery ( name="authentication.getByPrincipal | |
EnumRef jakarta.persistence.PessimisticLockScope that allow lock modes to be specified or used with the NamedQuery annotation. Since: JPA 2.0 Enum Constants | |
TypedQueryReference.getHints() - JPA Method JPA Method in jakarta.persistence.TypedQueryReference Map getHints () A map keyed by hint name of all hints specified via NamedQuery .hints or NamedNativeQuery.hints . Since: JPA 3.2 | |
AnnotationRef jakarta.persistence.QueryHint JPA Annotation QueryHint Implemented Interfaces: Annotation Used to supply a query property or hint to the NamedQuery or NamedNativeQuery annotation. Vendor-specific hints that are not recognized by a provider are ignored. Since: JPA 1.0 Public Annotation Attributes String name default null Name | |
EntityManager.createQuery(reference) - JPA Method is found to not be assignable to the specified type See Also: EntityManagerFactory.getNamedQueries NamedQuery NamedNativeQuery Since: JPA 1.0 | |
EntityManager.createNamedQuery(name) - JPA Method with the given name or if the query string is found to be invalid See Also: NamedQuery NamedNativeQuery Since: JPA 1.0 | |
UserException - Object User#2 belongs to another EntityManager CDI. Problem on method execution, which runs a NamedQuery : com.objectdb.o.UserException - Object 'com | |
com.objectdb.o.InternalException: Unexpected internal exception Hi, I am using objectdb.jar version 2.6.8 (installed via Maven). I am trying to authenticate a user. Initially, the database is empty. I have the following query: @javax.persistence. NamedQuery ( name = "getPersonByName", query = "SELECT _person FROM metamodel.user.Person as _person WHERE _person | |
ObjectDB needs "insert ignore" have to do this for inserting: @ NamedQuery ( name="isExistName", query="SELECT count(c) FROM Student c WHERE c |