ObjectDB Database Search

Jakarta Persistence (JPA) Method in jakarta.persistence.NamedNativeQuery QueryHint[] hints Query properties and hints . (May include vendor-specific query hints .) Default: {} Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.NamedQuery QueryHint[] hints (Optional) Query properties and hints . May include vendor-specific query hints . Default: {} Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.NamedStoredProcedureQuery QueryHint[] hints Query properties and hints . (May include vendor-specific query hints .) Default: {} Since: Jakarta Persistence (JPA) 1.0

and throw a LockTimeoutException if the lock cannot be acquired. Query hints Additional You can apply additional settings to queries by using hints . Supported query hints ObjectDB supports the following query hints : "jakarta.persistence.query.timeout" - Sets the maximum query execution time in

, it is returned from there. If a vendor-specific property or hint is not recognized, it is silently ignored. Parameters: entityClass - entity class properties - standard and vendor-specific properties and hints ... only statement-level rollback If a vendor-specific property or hint is not recognized, it is silently

provides a hint for the amount of space to reserve for the recovery file. ObjectDB might use ... miscellaneous database engine settings: The cache attribute provides a hint for the amount of memory

to the persistence provider within a @NamedQuery . Hints can control behavior such as query timeouts ... instances of the following interface: Represents a named query, including its name, result type, and hints

: flush mode. Since: Jakarta Persistence (JPA) 2.0 Map getHints () Get the properties and hints ... properties and hints . Since: Jakarta Persistence (JPA) 2.0 LockModeType getLockMode () Get the current ... ( String hintName , Object value ) Set a query property or hint . The hints elements may be used

(Lazy/Eager) at runtime using hints (e.g., jakarta.persistence.fetchgraph ). A nested graph

. The optional elements, lockMode and hints , provide a static replacement for the setLockMode and setHint

;  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 must be silently

) Since: Jakarta Persistence (JPA) 3.2 Public Instance Methods Map getHints () A map keyed by hint name of all hints specified via NamedQuery. hints or NamedNativeQuery. hints . Since: Jakarta Persistence (JPA) 1

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

;  String 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 the property or hint value - value for the property or hint Throws

Jakarta Persistence (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: Jakarta Persistence (JPA) 1.0

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: lockMode - lock mode entity - a managed entity instance

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: lockMode - lock mode entity - a managed entity

on the persistence provider runtime that data must be eagerly fetched. The LAZY strategy is a hint to the persistence ... is permitted to eagerly fetch data for which the LAZY strategy hint has been specified. Example

that the associated entity must be eagerly fetched. The LAZY strategy is a hint to the persistence ... may be null. This is a hint and is disregarded for primitive types; it may be used in schema generation

Jakarta Persistence (JPA) Method in jakarta.persistence.TypedQuery TypedQuery setTimeout (    Integer timeout ) Set the query timeout, in milliseconds. This is a hint , and is an alternative to setting the hint jakarta.persistence.query.timeout . Parameters: timeout - the timeout, in

Jakarta Persistence (JPA) Method in jakarta.persistence.StoredProcedureQuery StoredProcedureQuery setTimeout (    Integer timeout ) Set the query timeout, in milliseconds. This is a hint , and is an alternative to setting the hint jakarta.persistence.query.timeout . Parameters: timeout

=REFRESH . If a vendor-specific property or hint is not recognized, it is silently ignored. Parameters: entity - a managed entity instance properties - standard and vendor-specific properties and hints

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager Map getProperties() The properties and hints and their associated values which are in effect for this entity manager. Modifying ... of properties and hints currently in effect. Since: Jakarta Persistence (JPA) 2.0

strategy is a hint to the persistence provider runtime. If not specified, defaults to LAZY . Default

must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. If not

must be eagerly fetched. The LAZY strategy is a hint to the persistence provider runtime. If not specified

query definition. This includes configuration information such as max results, hints , flush mode, lock

timeout, in seconds. This is a hint . Parameters: timeout - the timeout, in seconds, or null to indicate

fetched. The LAZY strategy is a hint to the persistence provider runtime. If not specified

results, hints , flush mode, lock mode, result set mapping information, and information about stored

Jakarta Persistence (JPA) Method in jakarta.persistence.EntityTransaction void setTimeout (    Integer timeout ) Set the transaction timeout, in seconds. This is a hint . Parameters: timeout - the timeout, in seconds, or null to indicate that the database server should set the timeout Since: Jakarta Persistence (JPA) 3.2

and the locking mechanisms used by the provider, the hint may or may not be observed. Parameters: options

. The LAZY strategy is a hint to the persistence provider runtime. If not specified, defaults to EAGER

. The LAZY strategy is a hint to the persistence provider runtime. Default: FetchType.LAZY Since: Jakarta Persistence (JPA) 1.0

. The LAZY strategy is a hint to the persistence provider runtime. If not specified, defaults to EAGER

. However, there is a standardised query ' hint ' that can be setup to make the underlying DB lock a record for a specific time. The hint property is: "javax.persistence.lock.timeout" I have a situation ... however is lacking in this area (hence why they made it a ' hint ' - that should be considered non-portable

hint and check if it helps:  query.setHint("objectdb.result-fetch", "lazy ... by indexes without accessing the primary data. Currently this hint must be set at the query level (as demonstrated above) - but it should be supported in all other query hint scopes in future

and description properties must have been loaded on the query, ignoring the  fetch = FetchType.LAZY hint ... De Clercq LAZY in JPA (unlike EAGER ) is merely a hint , which JPA implementations may ignore ... is still a hint . ObjectDB (as other JPA providers) can only load one-to-one relationships lazily when entity classes are enhanced . support Support

, that can add a hint to which message the author is reply.     Sometimes, multiple replies confuse us in tracking the discussing topic, if a hint like this will be good: On 5/13/2011 11:46 AM, James007 wrote at floor 3: line 1 line 2 ...   gzdillon Lai Yang If no hint , just a link

consumption yet. Can you give us any any hints , which leads to the generation of these objects ... them.  Any kind of hints would help us to analyse/fix our problem.   We use version 2.6.9_08 in embedded mode. btc_es BTC EmbeddedSystems Small hint @ObjectDB (not related to this thread): I got

; I understand that the ObjectDb.conf value I specify ( ) is a HINT to the number of PAGs ... the configuration is indeed a hint . ObjectDB allows up to 80 additional pages (in addition to the pages

(when it is not an immediate exception)? Maybe a query hint to disable starting the threads ... client-server mode. The query hint to disable automatic starting of the backup thread

ours (there might be some additional issues from our side). Could you please give me a hint how we could avoid ... ; or does I miss something ?        can you please give me a hint

(unlike EAGER ) is considered in JPA as a hint and in some cases data is fetched eagerly regardless of the hint . This happens, for example, when ObjectDB uses reflection mode (classes are not enhanced

that is executed using a hint (will be explained in the next post). As you have several heavy queries ... 2 new query hints are introduced in build 2.7.6_01: 1. Selecting a query plan from the sorted list ... ) of the executed query plan (always 1 unless a hint is provided), the total number of query plans in

hint to request a specific preferred query as discussed in  issue #2379 . However, during the work on this issue it was found that the new query plan hint feature that was introduced in 2.7 ... )) [[objectdb.query-plan-text=index(ctso['(TC)'-'(TC)']] The 2nd query requires (using a hint ) to use

. We will consider adding such setting. You may be able to select a specific query plan using a hint ... this issue.   support Support You may be able to select a specific query plan using a hint . The problem ... combinations of fields. The hints seem to only let us select plans we want, not avoid plans we don't

the original queries but using query hints to override suboptimal query planning decisions ... discussing how to improve performance using query hints , but this requires more effort. support Support

less memory consumption by doing that, too. We would kindly ask you to give us some hints or advice ... then we can do that instead. Thanks for this hint ! Yes, only enhanced classes are used in this example

a query hint ( see issue #2379 ). Added logging when the number of allowed entity classes ... to select a query plan using a query hint ( see issue #2379 ). Fixed a critical bug in index based query