Package | Description |
---|---|
org.hibernate.ejb.internal | |
org.hibernate.engine.internal | |
org.hibernate.engine.loading.internal | |
org.hibernate.engine.spi | |
org.hibernate.envers.internal | |
org.hibernate.internal |
An internal package containing mostly implementations of central Hibernate APIs.
|
Class and Description |
---|
CollectionLoadContext
Represents state associated with the processing of a given
ResultSet
in regards to loading collections. |
EntityLoadContext
Tracks information about loading of entities specific to a given result set.
|
Class and Description |
---|
LoadContexts
Maps
result-sets to specific contextual data related to processing that result set
Implementation note: internally an IdentityMap is used to maintain the mappings mainly because I'd
rather not be dependent upon potentially bad Object.equals(java.lang.Object) and Object.hashCode() implementations on
the JDBC result sets
Considering the JDBC-redesign work, would further like this contextual info not mapped separately, but available
based on the result set being processed. |
Class and Description |
---|
CollectionLoadContext
Represents state associated with the processing of a given
ResultSet
in regards to loading collections. |
EntityLoadContext
Tracks information about loading of entities specific to a given result set.
|
LoadContexts
Maps
result-sets to specific contextual data related to processing that result set
Implementation note: internally an IdentityMap is used to maintain the mappings mainly because I'd
rather not be dependent upon potentially bad Object.equals(java.lang.Object) and Object.hashCode() implementations on
the JDBC result sets
Considering the JDBC-redesign work, would further like this contextual info not mapped separately, but available
based on the result set being processed. |
Class and Description |
---|
LoadContexts
Maps
result-sets to specific contextual data related to processing that result set
Implementation note: internally an IdentityMap is used to maintain the mappings mainly because I'd
rather not be dependent upon potentially bad Object.equals(java.lang.Object) and Object.hashCode() implementations on
the JDBC result sets
Considering the JDBC-redesign work, would further like this contextual info not mapped separately, but available
based on the result set being processed. |
Class and Description |
---|
CollectionLoadContext
Represents state associated with the processing of a given
ResultSet
in regards to loading collections. |
EntityLoadContext
Tracks information about loading of entities specific to a given result set.
|
Class and Description |
---|
CollectionLoadContext
Represents state associated with the processing of a given
ResultSet
in regards to loading collections. |
EntityLoadContext
Tracks information about loading of entities specific to a given result set.
|
Copyright © 2018 JBoss by Red Hat. All rights reserved.