ObjectDB ObjectDB

Internal Website Search

11-20 of 120 resultsRefresh
12

JPA Named Queries

and hints, provide static replacement for the setLockMode and setHint methods. Every @NamedQuery annotation
10

setHint(hintName, value)

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 ... timeout hint. Depending on the database in use and the locking mechanisms used by the provider, this hint
10

setHint(hintName, value)

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 ... on the standard timeout hint. Depending on the database in use and the locking mechanisms used by
9

javax.persistence.QueryHint

javax.persistence Annotation QueryHint Target: 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 String name Name of the hint. Name of the hint. Since: JPA 1.0 String
7

find(entityClass, primaryKey, lockMode, properties)

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. Parameters
7

refresh(entity, lockMode, properties)

-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. Parameters
7

setProperty(propertyName, value)

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 argument is not valid for the implementation Since: JPA 2.0
7

lock(entity, lockMode, properties)

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
7

find(entityClass, primaryKey, lockMode, properties)

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. Parameters: entityClass
0

find(entityClass, primaryKey, lockMode, properties)

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. Parameters: entityClass

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support