com.blazebit.persistence.ConfigurationProperties

public final class ConfigurationProperties
extends Object

Since:: 1.0.0
Author:: Christian Beikov, Moritz Becker

Field Summary

Fields
Modifier and Type	Field	Description
`static String`	`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.
`static String`	`EXPRESSION_CACHE_CLASS`	The full qualified expression cache implementation class name.
`static String`	`EXPRESSION_OPTIMIZATION`	If set to false, no expression optimization takes place.
`static String`	`IMPLICIT_GROUP_BY_FROM_HAVING`	If set to false, no implicit group by clauses will be generated from the HAVING part of the query.
`static String`	`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.
`static String`	`IMPLICIT_GROUP_BY_FROM_SELECT`	If set to false, no implicit group by clauses will be generated from the SELECT part of the query.
`static String`	`INLINE_COUNT_QUERY`	If set to true, the count query in a `PaginatedCriteriaBuilder` is inlined into the id or object query as select item.
`static String`	`INLINE_CTES`	If set to true, the CTE queries are inlined by default.
`static String`	`INLINE_ID_QUERY`	If set to true, the id query in a `PaginatedCriteriaBuilder` is inlined into the object query as subquery.
`static String`	`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.
`static String`	`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.
`static String`	`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.
`static String`	`SIZE_TO_COUNT_TRANSFORMATION`	If set to false, uses of SIZE will always be transformed to subqueries.
`static String`	`VALUES_CLAUSE_FILTER_NULLS`	If set to false, tuples of a VALUES clause with all null values won't be filtered out.

Method Summary

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details
- COMPATIBLE_MODE
  
  public static final String 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 are true or false.
  
  Since:
  
  1.0.5
  
  See Also:
  
  Constant Field Values
- RETURNING_CLAUSE_CASE_SENSITIVE
  
  public static final String 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 are true or false. The property can be changed for a criteria builder before generating the query.
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- SIZE_TO_COUNT_TRANSFORMATION
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before generating the query.
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- IMPLICIT_GROUP_BY_FROM_SELECT
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before generating the query.
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- IMPLICIT_GROUP_BY_FROM_HAVING
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before generating the query.
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- IMPLICIT_GROUP_BY_FROM_ORDER_BY
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before generating the query.
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- EXPRESSION_OPTIMIZATION
  
  public static final String EXPRESSION_OPTIMIZATION
  
  If set to false, no expression optimization takes place. Valid values for this property are true or false. Default is true
  
  Since:
  
  1.1.0
  
  See Also:
  
  Constant Field Values
- EXPRESSION_CACHE_CLASS
  
  public static final String EXPRESSION_CACHE_CLASS
  
  The full qualified expression cache implementation class name.
  
  Since:
  
  1.2.0
  
  See Also:
  
  Constant Field Values
- VALUES_CLAUSE_FILTER_NULLS
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before using the VALUES clause.
  
  Since:
  
  1.2.0
  
  See Also:
  
  Constant Field Values
- PARAMETER_AS_LITERAL_RENDERING
  
  public static final String 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 are true or false. Default is true The property can be changed for a criteria builder before constructing a query.
  
  Since:
  
  1.2.0
  
  See Also:
  
  Constant Field Values
- OPTIMIZED_KEYSET_PREDICATE_RENDERING
  
  public static final String 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 is true The property can be changed for a criteria builder before constructing a query.
  
  Since:
  
  1.2.0
  
  See Also:
  
  Constant Field Values
- INLINE_ID_QUERY
  
  public static final String INLINE_ID_QUERY
  
  If set to true, the id query in a PaginatedCriteriaBuilder is inlined into the object query as subquery. Valid values for this property are true, false or auto. Default is auto 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:
  
  PaginatedCriteriaBuilder.withInlineIdQuery(boolean), Constant Field Values
- INLINE_COUNT_QUERY
  
  public static final String INLINE_COUNT_QUERY
  
  If set to true, the count query in a PaginatedCriteriaBuilder is inlined into the id or object query as select item. Valid values for this property are true, false or auto. Default is auto 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:
  
  PaginatedCriteriaBuilder.withInlineCountQuery(boolean), Constant Field Values
- INLINE_CTES
  
  public static final String INLINE_CTES
  
  If set to true, the CTE queries are inlined by default. Valid values for this property are true, false or auto. Default is true which will always inline non-recursive CTEs. The auto 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:
  
  CTEBuilder.with(Class, boolean), CTEBuilder.with(Class, CriteriaBuilder, boolean), Constant Field Values

Class ConfigurationProperties

Field Summary

Method Summary

Methods inherited from class java.lang.Object

Field Details