Package io.quarkus.hibernate.orm.deployment

Interface HibernateOrmConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitQuery

Enclosing interface:

HibernateOrmConfigPersistenceUnit

public static interface HibernateOrmConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitQuery

Nested Class Summary

Nested Classes

Modifier and Type	Interface	Description
static enum	HibernateOrmConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitQuery.NullOrdering

Field Summary

Fields

Modifier and Type	Field	Description
static final int	DEFAULT_QUERY_PLAN_CACHE_MAX_SIZE

Method Summary

Modifier and Type	Method	Description
HibernateOrmConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitQuery.NullOrdering	defaultNullOrdering()	Default precedence of null values in `ORDER BY` clauses.
boolean	failOnPaginationOverCollectionFetch()	When limits cannot be applied on the database side, trigger an exception instead of attempting badly-performing in-memory result set limits.
boolean	inClauseParameterPadding()	Enables IN clause parameter padding which improves statement caching.
default boolean	isAnyPropertySet()
int	queryPlanCacheMaxSize()	The maximum size of the query plan cache.

Field Details

DEFAULT_QUERY_PLAN_CACHE_MAX_SIZE

static final int DEFAULT_QUERY_PLAN_CACHE_MAX_SIZE

See Also:

• Constant Field Values

Method Details

queryPlanCacheMaxSize

@WithDefault("2048")
int queryPlanCacheMaxSize()

The maximum size of the query plan cache. see #"hibernate.query.plan_cache_max_size"

defaultNullOrdering

@WithDefault("none")
HibernateOrmConfigPersistenceUnit.HibernateOrmConfigPersistenceUnitQuery.NullOrdering defaultNullOrdering()

Default precedence of null values in `ORDER BY` clauses. Valid values are: `none`, `first`, `last`.

inClauseParameterPadding

@WithDefault("true")
boolean inClauseParameterPadding()

Enables IN clause parameter padding which improves statement caching.

failOnPaginationOverCollectionFetch

@WithDefault("false")
boolean failOnPaginationOverCollectionFetch()

When limits cannot be applied on the database side, trigger an exception instead of attempting badly-performing in-memory result set limits. When pagination is used in combination with a fetch join applied to a collection or many-valued association, the limit must be applied in-memory instead of on the database. This should be avoided as it typically has terrible performance characteristics.

isAnyPropertySet

default boolean isAnyPropertySet()