ObjectDB Database Search
1-50 of 123 resultsSetting and Tuning of JPA Queries Hints Additional settings can be applied to queries via hints . Supported Query Hints ObjectDB supports the following query hints : "javax.persistence.query.timeout" - sets maximum query execution time ... . Setting Query Hint (Scopes) Query hints can be set in the following scopes (from global to local | |
query hint some years ago there was a chat around query hints http://www.objectdb.com/issue/2417 we are currently trying that with the latest version but we do not see that our hint is used this is the query ... )']] but the index that is in the hint is not used the MultiVarPlan that is listed shows our index in | |
javax.persistence.NamedNativeQuery.hints JPA Annotation Attribute in javax.persistence.NamedNativeQuery QueryHint [] hints default {} Query properties and hints . (May include vendor-specific query hints .) Since: JPA 1.0 | |
javax.persistence.NamedQuery.hints JPA Annotation Attribute in javax.persistence.NamedQuery QueryHint [] hints default {} (Optional) Query properties and hints . May include vendor-specific query hints . Since: JPA 1.0 | |
javax.persistence.NamedStoredProcedureQuery.hints JPA Annotation Attribute in javax.persistence.NamedStoredProcedureQuery QueryHint [] hints default {} Query properties and hints . (May include vendor-specific query hints .) Since: JPA 2.1 | |
Locking in JPA occurs a LockTimeoutException is thrown immediately. The "javax.persistence.lock.timeout" hint ... ;The hint can be set in several scopes: For the entire persistence unit - using a persistence.xml   ... . setProperty ("javax.persistence.lock.timeout", 4000); In addition, the hint can be set for a specific | |
Database Management Settings and the database file can improve performance. The max attribute is a hint that specifies the space ... engine settings: The cache attribute is a hint that specifies the amount of memory that is used | |
JPA Named Queries itself and are demonstrated above. The two optional elements, lockMode and hints , provide static replacement | |
Read only hint for query Second thing after @FetchGroup I've found is read-only hint for EM. You can specify this hint to EM when executing query meaning that returned data will never be edited or persisted. My understanding of this is that each entity returned from query is in detached state as default state. query | |
javax.persistence.EntityManager causes only statement-level rollback If a vendor-specific property or hint is not recognized, it is silently ignored. Portable applications should not rely on the standard timeout hint . Depending on the database in use and the locking mechanisms used by the provider, the hint may or may not be observed | |
javax.persistence.Query manager. Return: flush mode Since: JPA 2.0 Map getHints () Get the properties and hints and associated values that are in effect for the query instance. Return: query properties and hints Since: JPA 2.0 ... Since: JPA 1.0 Query setHint (String hintName, Object value) Set a query property or hint | |
javax.persistence.StoredProcedureQuery Inherited from: Query Since: JPA 2.0 Map getHints () Get the properties and hints and associated values that are in effect for the query instance. Return: query properties and hints Inherited from: Query ... hintName, Object value) Set a query property or hint . The hints elements may be used | |
javax.persistence.TypedQuery and hints and associated values that are in effect for the query instance. Return: query properties and hints Inherited from: Query Since: JPA 2.0 LockModeType getLockMode () Get the current lock mode ... setHint (String hintName, Object value) Set a query property or hint . The hints | |
Query.setHint(hintName,value) - JPA Method; Object value ) Set a query property or hint . The hints elements may be used to specify query properties and hints . Properties defined by this specification must be observed by the provider. Vendor-specific hints that are not recognized by a provider must be silently ignored. Portable | |
StoredProcedureQuery.setHint(hintName,value) - JPA Method;String hintName, Object value ) Set a query property or hint . The hints elements may be used to specify query properties and hints . Properties defined by this specification must be observed by the provider. Vendor-specific hints that are not recognized by a provider | |
TypedQuery.setHint(hintName,value) - JPA Method, Object value ) Set a query property or hint . The hints elements may be used to specify query properties and hints . Properties defined by this specification must be observed by the provider. Vendor-specific hints that are not recognized by a provider must be silently ignored | |
javax.persistence.NamedStoredProcedureQuery. The hints element may be used to specify query properties and hints . Properties defined by this specification must be observed by the provider. Vendor-specific hints that are not recognized by a provider ... Public Annotation Attributes QueryHint [] hints default {} Query properties and hints . (May include | |
EntityManager.find(entityClass,primaryKey,lockMode,properties) - JPA Method If a vendor-specific property or hint is not recognized, it is silently ignored. Portable applications should not rely on the standard timeout hint . Depending on the database in use and the locking mechanisms used by the provider, the hint may or may not be observed. Parameters: entityClass - entity | |
EntityManager.lock(entity,lockMode,properties) - JPA Method-specific property or hint is not recognized, it is silently ignored. Portable applications should not rely on the standard timeout hint . Depending on the database in use and the locking mechanisms used by the provider, the hint may or may not be observed. Parameters: entity - entity instance lockMode | |
EntityManager.refresh(entity,lockMode,properties) - JPA Method property or hint is not recognized, it is silently ignored. Portable applications should not rely on the standard timeout hint . Depending on the database in use and the locking mechanisms used by the provider, the hint may or may not be observed. Parameters: entity - entity instance lockMode - lock | |
EntityManager.setProperty(propertyName,value) - JPA Method;propertyName, Object value ) Set an entity manager property or hint . If a vendor-specific property or hint is not recognized, it is silently ignored. Parameters: propertyName - name of property or hint value - value for property or hint Throws: IllegalArgumentException - if the second | |
javax.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 ... of the hint . Since: JPA 1.0 String value default null Value of the hint . Since: JPA 1.0 | |
javax.persistence.NamedNativeQuery QueryHint [] hints default {} Query properties and hints . (May include vendor-specific query hints | |
javax.persistence.NamedQuery Attributes QueryHint [] hints default {} (Optional) Query properties and hints . May include vendor-specific query hints . Since: JPA 1.0 LockModeType lockMode default NONE (Optional) The lock mode type | |
javax.persistence.Basic strategy is a hint to the persistence provider runtime. If not specified, defaults to EAGER ... may be null. This is a hint and is disregarded for primitive types; it may be used in schema | |
EntityManager.find(entityClass,primaryKey,properties) - JPA Method-specific property or hint is not recognized, it is silently ignored. Parameters: entityClass - entity class primaryKey - primary key properties - standard and vendor-specific properties and hints Return | |
EntityManager.refresh(entity,properties) - JPA Method property or hint is not recognized, it is silently ignored. Parameters: entity - entity instance properties - standard and vendor-specific properties and hints Throws: IllegalArgumentException | |
EntityManager.getProperties() - JPA Method JPA Method in javax.persistence.EntityManager Map getProperties () Get the properties and hints and associated values that are in effect for the entity manager. Changing the contents of the map does not change the configuration in effect. Return: map of properties and hints in effect for entity manager Since: JPA 2.0 | |
javax.persistence.FetchType on the persistence provider runtime that data must be eagerly fetched. The LAZY strategy is a hint ... . The implementation is permitted to eagerly fetch data for which the LAZY strategy hint has been specified. Example | |
Query.getHints() - JPA Method JPA Method in javax.persistence.Query Map getHints () Get the properties and hints and associated values that are in effect for the query instance. Return: query properties and hints Since: JPA 2.0 | |
javax.persistence.Basic.fetch fetched. The LAZY strategy is a hint to the persistence provider runtime. If not specified, defaults to EAGER . Since: JPA 1.0 | |
javax.persistence.Basic.optional JPA Annotation Attribute in javax.persistence.Basic boolean optional default true (Optional) Defines whether the value of the field or property may be null. This is a hint and is disregarded for primitive types; it may be used in schema generation. If not specified, defaults to true . Since: JPA 1.0 | |
javax.persistence.ElementCollection strategy is a hint to the persistence provider runtime. Since: JPA 2.0 Class targetClass default | |
javax.persistence.ElementCollection.fetch fetched. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA 2.0 | |
javax.persistence.EntityManagerFactory results, hints , flush mode, lock mode, result set mapping information, and information about stored | |
EntityManagerFactory.addNamedQuery(name,query) - JPA Method definition. This includes configuration information such as max results, hints , flush mode, lock mode | |
javax.persistence.ManyToMany runtime that the associated entities must be eagerly fetched. The LAZY strategy is a hint | |
javax.persistence.ManyToMany.fetch. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA 1.0 | |
javax.persistence.ManyToOne is a hint to the persistence provider runtime. Since: JPA 1.0 boolean optional default true | |
javax.persistence.ManyToOne.fetch. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA 1.0 | |
javax.persistence.OneToMany that the associated entities must be eagerly fetched. The LAZY strategy is a hint to the persistence provider | |
javax.persistence.OneToMany.fetch. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA 1.0 | |
javax.persistence.OneToOne must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA | |
javax.persistence.OneToOne.fetch. The LAZY strategy is a hint to the persistence provider runtime. Since: JPA 1.0 | |
javax.persistence.QueryHint.name JPA Annotation Attribute in javax.persistence.QueryHint String name default null Name of the hint . Since: JPA 1.0 | |
javax.persistence.QueryHint.value JPA Annotation Attribute in javax.persistence.QueryHint String value default null Value of the hint . Since: JPA 1.0 | |
javax.jdo.PersistenceManager at transaction completion. This method allows the application to explicitly provide a hint | |
PersistenceManager.evict(pc) - JDO Method JDO Method in javax.jdo.PersistenceManager void evict ( Object pc ) Mark an instance as no longer needed in the cache. Eviction is normally done automatically by the PersistenceManager at transaction completion. This method allows the application to explicitly provide a hint | |
javax.jdo.Query and provide a hint to the query to prepare and optimize an execution plan. Since: JDO 1.0 void | |
Query.compile() - JDO Method JDO Method in javax.jdo.Query void compile () Verify the elements of the query and provide a hint to the query to prepare and optimize an execution plan. Since: JDO 1.0 |