Home » Search

About performance

81-90 of 200Refresh
JPA Doc
3

javax.persistence.criteria.Subquery

Returns: selection item Since: JPA 2.0 Expression as(Class type) Perform a typecast upon the expression, returning a new expression object. Perform a typecast upon the expression, returning
JPA Doc
3

javax.persistence.InheritanceType

than the fields that are common to the parent class, and a join is performed to instantiate the subclass ... that are common to the parent class, and a join is performed to instantiate the subclass. Since: JPA
JPA Doc
3

lock(entity, lockMode)

, the persistence provider must also perform optimistic version checks when obtaining the database lock ... - if the entity does not exist in the database when pessimistic locking is performed
JPA Doc
3

lock(entity, lockMode, properties)

is specified and the entity contains a version attribute, the persistence provider must also perform ... - if the entity does not exist in the database when pessimistic locking is performed
Issue
2

Best practise loading big data

Hello, currently we take some effort to improve the overall performance of our product. ObjectDB is the main data provider within our solution. In the past we often discovered performance problems ... them but we could not see some performance improvement or less memory consumption by doing
JPA Doc
2

as(type)

Method javax.persistence.criteria.Expression Expression as(   Class type ) Perform a typecast upon the expression, returning a new expression object. This method does not cause type conversion: the runtime type is not changed. Warning: may result in a runtime failure. Parameters: type
JDO Doc
2

checkAuthorizedStateManager(sm)

("setStateManager"). To improve performance, first the set of authorized classes is checked, and if not present
Forum
2

Extended mapping-definitions

'. Please clarify: Is it only for improving performance, or do you also expect a change in functionality? How exactly performance should be improved if the functionality remains the same? You suggest storing instances of one class in different 'tables'. -> Yes Is it only for improving performance
JPA Doc
2

find(entityClass, primaryKey, lockMode)

provider must perform optimistic version checks when obtaining the database lock. If these checks fail
JPA Doc
2

find(entityClass, primaryKey, lockMode, properties)

and the entity has a version attribute, the persistence provider must perform optimistic version