Top Fields Constructors Methods
org.hibernate.query.sqm.internal

public Class SqmCreationOptionsStandard

extends Object
implements SqmCreationOptions
Class Inheritance
All Implemented Interfaces
org.hibernate.query.hql.spi.SqmCreationOptions
Imports
org.hibernate.query.hql.spi.SqmCreationOptions, org.hibernate.query.spi.QueryEngineOptions
Author
Steve Ebersole

Field Summary

Modifier and TypeField and Description
private final QueryEngineOptions
queryEngineOptions

Constructor Summary

AccessConstructor and Description
public
SqmCreationOptionsStandard(QueryEngineOptions queryEngineOptions)

Method Summary

Modifier and TypeMethod and Description
public boolean
useStrictJpaCompliance()

Implements org.hibernate.query.hql.spi.SqmCreationOptions.useStrictJpaCompliance.

Should we interpret the query strictly according to the JPA specification?
Inherited from java.lang.Object:
cloneequalsfinalizegetClasshashCodenotifynotifyAlltoStringwaitwaitwait

Field Detail

queryEngineOptionsback to summary
private final QueryEngineOptions queryEngineOptions

Constructor Detail

SqmCreationOptionsStandardback to summary
public SqmCreationOptionsStandard(QueryEngineOptions queryEngineOptions)

Method Detail

useStrictJpaComplianceback to summary
public boolean useStrictJpaCompliance()

Implements org.hibernate.query.hql.spi.SqmCreationOptions.useStrictJpaCompliance.

Doc from org.hibernate.query.hql.spi.SqmCreationOptions.useStrictJpaCompliance.

Should we interpret the query strictly according to the JPA specification? In other words, should Hibernate "extensions" to the query language be disallowed?

Annotations
@Override