public class LoadQueryInfluencers
extends java.lang.Object
implements java.io.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) |
Modifier and Type | Method and Description |
---|---|
void |
disableFetchProfile(java.lang.String name) |
void |
disableFilter(java.lang.String filterName) |
void |
enableFetchProfile(java.lang.String name) |
Filter |
enableFilter(java.lang.String filterName) |
EffectiveEntityGraph |
getEffectiveEntityGraph() |
java.util.Set<java.lang.String> |
getEnabledFetchProfileNames() |
Filter |
getEnabledFilter(java.lang.String filterName) |
java.util.Set<java.lang.String> |
getEnabledFilterNames()
Returns an unmodifiable Set of enabled filter names.
|
java.util.Map<java.lang.String,Filter> |
getEnabledFilters() |
javax.persistence.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(java.lang.String filterParameterName) |
java.lang.Object |
getFilterParameterValue(java.lang.String filterParameterName) |
java.lang.String |
getInternalFetchProfile() |
javax.persistence.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() . |
SessionFactoryImplementor |
getSessionFactory() |
boolean |
hasEnabledFetchProfiles() |
boolean |
hasEnabledFilters() |
boolean |
isFetchProfileEnabled(java.lang.String name) |
static java.lang.String[] |
parseFilterParameterName(java.lang.String filterParameterName) |
void |
setFetchGraph(javax.persistence.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(java.lang.String internalFetchProfile) |
void |
setLoadGraph(javax.persistence.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() . |
public static final LoadQueryInfluencers NONE
public LoadQueryInfluencers()
public LoadQueryInfluencers(SessionFactoryImplementor sessionFactory)
public SessionFactoryImplementor getSessionFactory()
public java.lang.String getInternalFetchProfile()
public void setInternalFetchProfile(java.lang.String internalFetchProfile)
public boolean hasEnabledFilters()
public java.util.Map<java.lang.String,Filter> getEnabledFilters()
public java.util.Set<java.lang.String> getEnabledFilterNames()
public Filter getEnabledFilter(java.lang.String filterName)
public Filter enableFilter(java.lang.String filterName)
public void disableFilter(java.lang.String filterName)
public java.lang.Object getFilterParameterValue(java.lang.String filterParameterName)
public Type getFilterParameterType(java.lang.String filterParameterName)
public static java.lang.String[] parseFilterParameterName(java.lang.String filterParameterName)
public boolean hasEnabledFetchProfiles()
public java.util.Set<java.lang.String> getEnabledFetchProfileNames()
public boolean isFetchProfileEnabled(java.lang.String name) throws UnknownProfileException
UnknownProfileException
public void enableFetchProfile(java.lang.String name) throws UnknownProfileException
UnknownProfileException
public void disableFetchProfile(java.lang.String name) throws UnknownProfileException
UnknownProfileException
public EffectiveEntityGraph getEffectiveEntityGraph()
@Deprecated public javax.persistence.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(javax.persistence.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 javax.persistence.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(javax.persistence.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()
.EffectiveEntityGraph
Copyright © 2001-2019 Red Hat, Inc. All Rights Reserved.