ObjectDB Database Search

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

;  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

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

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

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

. 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

isn't a problem. The GUI related methods will add implicit a '%' character. Additional hint : 

without performance penalty. You can change this behavior by setting the  "objectdb.result-fetch" query hint

( unknown source ) xirt Sylvain You can set a query execution timeout as a query hint . The many

. It is really tiresome. As we bought the license years ago there was hinted at a automatic

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