Package com.blazebit.persistence
Class ConfigurationProperties
java.lang.Object
com.blazebit.persistence.ConfigurationProperties
- Since:
- 1.0.0
- Author:
- Christian Beikov, Moritz Becker
-
Field Summary
Modifier and TypeFieldDescriptionstatic final String
We added a flag to enable a JPA compatible mode because we allow to make use of many vendor specific extensions which maybe aren't portable.static final String
If set to true, JPA Criteria predicates are wrapped in a negation predicate instead of copied with negation being propagated.static final String
If set to true, values passed to the JPACriteriaBuilder
API are rendered as parameters, otherwise values are rendered as literals.static final String
The fully qualified expression cache implementation class name.static final String
If set to false, no expression optimization takes place.static final String
If set to false, no implicit group by clauses will be generated from the HAVING part of the query.static final String
If set to false, no implicit group by clauses will be generated from the ORDER BY part of the query.static final String
If set to false, no implicit group by clauses will be generated from the SELECT part of the query.static final String
If set to true, the count query in aPaginatedCriteriaBuilder
is inlined into the id or object query as select item.static final String
If set to true, the CTE queries are inlined by default.static final String
If set to true, the id query in aPaginatedCriteriaBuilder
is inlined into the object query as subquery.static final String
If set to true, the keyset predicate is rendered in an optimized form so that database optimizers are more likely to use indices.static final String
If set to false, parameters are always rendered as such, otherwise the values might get inlined when no type can be inferred.static final String
If set to true, the query plans are cached and reused.static final String
Some databases require case sensitivity for attribute paths in the returning clause (unlike PostgreSQL which requires case insensitivity for column names in returning clause) By default the returning clause is case sensitive.static final String
If set to false, uses of SIZE will always be transformed to subqueries.static final String
If set to false, tuples of a VALUES clause with all null values won't be filtered out. -
Method Summary
-
Field Details
-
COMPATIBLE_MODE
We added a flag to enable a JPA compatible mode because we allow to make use of many vendor specific extensions which maybe aren't portable. By enabling the compatible mode functionality is restricted but more portable. By default the compatible mode is disabled because most JPA providers support the same extensions. Valid values for this property aretrue
orfalse
.- Since:
- 1.0.5
- See Also:
-
RETURNING_CLAUSE_CASE_SENSITIVE
Some databases require case sensitivity for attribute paths in the returning clause (unlike PostgreSQL which requires case insensitivity for column names in returning clause) By default the returning clause is case sensitive. Valid values for this property aretrue
orfalse
. The property can be changed for a criteria builder before generating the query.- Since:
- 1.1.0
- See Also:
-
SIZE_TO_COUNT_TRANSFORMATION
If set to false, uses of SIZE will always be transformed to subqueries. By default the size to count transformation is enabled. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before generating the query.- Since:
- 1.1.0
- See Also:
-
IMPLICIT_GROUP_BY_FROM_SELECT
If set to false, no implicit group by clauses will be generated from the SELECT part of the query. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before generating the query.- Since:
- 1.1.0
- See Also:
-
IMPLICIT_GROUP_BY_FROM_HAVING
If set to false, no implicit group by clauses will be generated from the HAVING part of the query. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before generating the query.- Since:
- 1.1.0
- See Also:
-
IMPLICIT_GROUP_BY_FROM_ORDER_BY
If set to false, no implicit group by clauses will be generated from the ORDER BY part of the query. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before generating the query.- Since:
- 1.1.0
- See Also:
-
EXPRESSION_OPTIMIZATION
If set to false, no expression optimization takes place. Valid values for this property aretrue
orfalse
. Default istrue
- Since:
- 1.1.0
- See Also:
-
EXPRESSION_CACHE_CLASS
The fully qualified expression cache implementation class name.- Since:
- 1.2.0
- See Also:
-
VALUES_CLAUSE_FILTER_NULLS
If set to false, tuples of a VALUES clause with all null values won't be filtered out. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before using the VALUES clause.- Since:
- 1.2.0
- See Also:
-
PARAMETER_AS_LITERAL_RENDERING
If set to false, parameters are always rendered as such, otherwise the values might get inlined when no type can be inferred. Valid values for this property aretrue
orfalse
. Default istrue
The property can be changed for a criteria builder before constructing a query.- Since:
- 1.2.0
- See Also:
-
OPTIMIZED_KEYSET_PREDICATE_RENDERING
If set to true, the keyset predicate is rendered in an optimized form so that database optimizers are more likely to use indices. See https://github.com/Blazebit/blaze-persistence/issues/419 Default istrue
The property can be changed for a criteria builder before constructing a query.- Since:
- 1.2.0
- See Also:
-
INLINE_ID_QUERY
If set to true, the id query in aPaginatedCriteriaBuilder
is inlined into the object query as subquery. Valid values for this property aretrue
,false
orauto
. Default isauto
which will make use of inlining if the JPA provider and DBMS dialect support it. The property can be changed for a criteria builder before generating the query.- Since:
- 1.4.1
- See Also:
-
INLINE_COUNT_QUERY
If set to true, the count query in aPaginatedCriteriaBuilder
is inlined into the id or object query as select item. Valid values for this property aretrue
,false
orauto
. Default isauto
which will make use of inlining if the JPA provider and DBMS dialect support it. The property can be changed for a criteria builder before generating the query.- Since:
- 1.4.1
- See Also:
-
INLINE_CTES
If set to true, the CTE queries are inlined by default. Valid values for this property aretrue
,false
orauto
. Default istrue
which will always inline non-recursive CTEs. Theauto
configuration will only make use of inlining if the JPA provider and DBMS dialect support/require it. The property can be changed for a criteria builder before constructing a query.- Since:
- 1.4.1
- See Also:
-
QUERY_PLAN_CACHE_ENABLED
If set to true, the query plans are cached and reused. Valid values for this property aretrue
andfalse
. Default istrue
. This configuration option currently only takes effect when Hibernate is used as JPA provider. The property can be changed for a criteria builder before constructing a query.- Since:
- 1.5.0
- See Also:
-
CRITERIA_NEGATION_WRAPPER
If set to true, JPA Criteria predicates are wrapped in a negation predicate instead of copied with negation being propagated. Valid values for this property aretrue
andfalse
. Default istrue
.- Since:
- 1.6.3
- See Also:
-
CRITERIA_VALUE_AS_PARAMETER
If set to true, values passed to the JPACriteriaBuilder
API are rendered as parameters, otherwise values are rendered as literals. Valid values for this property aretrue
andfalse
. Default istrue
.- Since:
- 1.6.3
- See Also:
-