public class LoadQueryInfluencers extends Object implements Serializable
| Modifier and Type | Field and Description |
|---|---|
static LoadQueryInfluencers |
NONE
Static reference useful for cases where we are creating load SQL
outside the context of any influencers.
|
| Constructor and Description |
|---|
LoadQueryInfluencers() |
LoadQueryInfluencers(SessionFactoryImplementor sessionFactory) |
LoadQueryInfluencers(SessionFactoryImplementor sessionFactory,
Boolean readOnly) |
| Modifier and Type | Method and Description |
|---|---|
void |
disableFetchProfile(String name) |
void |
disableFilter(String filterName) |
void |
enableFetchProfile(String name) |
Filter |
enableFilter(String filterName) |
EffectiveEntityGraph |
getEffectiveEntityGraph() |
Set<String> |
getEnabledFetchProfileNames() |
Filter |
getEnabledFilter(String filterName) |
Set<String> |
getEnabledFilterNames()
Returns an unmodifiable Set of enabled filter names.
|
Map<String,Filter> |
getEnabledFilters() |
EntityGraph |
getFetchGraph()
Deprecated.
(since 5.4)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph(). |
Type |
getFilterParameterType(String filterParameterName) |
Object |
getFilterParameterValue(String filterParameterName) |
String |
getInternalFetchProfile() |
EntityGraph |
getLoadGraph()
Deprecated.
(since 5.4)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph(). |
Boolean |
getReadOnly() |
SessionFactoryImplementor |
getSessionFactory() |
boolean |
hasEnabledFetchProfiles() |
boolean |
hasEnabledFilters() |
boolean |
isFetchProfileEnabled(String name) |
static String[] |
parseFilterParameterName(String filterParameterName) |
void |
setFetchGraph(EntityGraph fetchGraph)
Deprecated.
(since 5.4)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph(). |
void |
setInternalFetchProfile(String internalFetchProfile) |
void |
setLoadGraph(EntityGraph loadGraph)
Deprecated.
(since 5.4)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph(). |
void |
setReadOnly(Boolean readOnly) |
public static final LoadQueryInfluencers NONE
public LoadQueryInfluencers()
public LoadQueryInfluencers(SessionFactoryImplementor sessionFactory)
public LoadQueryInfluencers(SessionFactoryImplementor sessionFactory, Boolean readOnly)
public SessionFactoryImplementor getSessionFactory()
public String getInternalFetchProfile()
public void setInternalFetchProfile(String internalFetchProfile)
public boolean hasEnabledFilters()
public Set<String> getEnabledFilterNames()
public void disableFilter(String filterName)
public static String[] parseFilterParameterName(String filterParameterName)
public boolean hasEnabledFetchProfiles()
public boolean isFetchProfileEnabled(String name) throws UnknownProfileException
UnknownProfileExceptionpublic void enableFetchProfile(String name) throws UnknownProfileException
UnknownProfileExceptionpublic void disableFetchProfile(String name) throws UnknownProfileException
UnknownProfileExceptionpublic EffectiveEntityGraph getEffectiveEntityGraph()
@Deprecated public EntityGraph getFetchGraph()
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph().EffectiveEntityGraph@Deprecated public void setFetchGraph(EntityGraph fetchGraph)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph().EffectiveEntityGraph@Deprecated public EntityGraph getLoadGraph()
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph().EffectiveEntityGraph@Deprecated public void setLoadGraph(EntityGraph loadGraph)
getFetchGraph(), getLoadGraph(), setFetchGraph(javax.persistence.EntityGraph)
and setLoadGraph(javax.persistence.EntityGraph) (as well as JPA itself honestly) all make it very unclear that
there can be only one graph applied at any one time and that that graph is *either* a load or
a fetch graph. These have all been replaced with getEffectiveEntityGraph().EffectiveEntityGraphpublic Boolean getReadOnly()
public void setReadOnly(Boolean readOnly)
Copyright © 2001-2022 Red Hat, Inc. All Rights Reserved.