CollectionType

Reconstruct the object from its cached "disassembled" state.

Perform a Comparator style comparison between values

Return a deep copy of the persistent state, stopping at entities and at collections.

Return a cacheable "disassembled" representation of the object.

Parse the XML representation of an instance.

Get the entity name of the associated entity

Get the "persister" for this association - a class or collection persister

instantiate a collection wrapper (called when loading an object)

How many columns are used to persist this type. Always the same as sqlTypes(mapping).length

Get the Hibernate type of the collection elements

Get an iterator over the element set of the collection, which may not yet be wrapped

Get the foreign key directionality of this association

Get a hash code, consistent with persistence "equality". Again for most types the normal usage is to delegate to the value's #hashCode.

Get the id value from the owning entity key, usually the same as the key, but might be some other property, in the case of property-ref

Get the key value from the owning entity instance, usually the identifier, but might be some other unique key, in the case of property-ref

Get the name of a property in the owning entity that provides the join key (null if the identifier)

Returns the abbreviated name of the type.

Get the "filtering" SQL fragment that is applied in the SQL on clause, in addition to the usual join condition

The name of a unique property of the associated entity that provides the join key (null if the identifier of an entity, or key of a collection)

Retrieve an instance of the mapped class, or the identifier of an entity or collection, from a JDBC resultset. This is useful for 2-phase property initialization - the second phase is a call to resolveIdentifier().

Instantiate an uninitialized collection wrapper or holder. Callers MUST add the holder to the persistence context!

Instantiate an empty instance of the "underlying" collection (not a wrapper), but with the given anticipated size (i.e. accounting for initial capacity and perhaps load factor).

We always need to dirty check the collection because we sometimes need to incremement version number of owner and also because of how assemble/disassemble is implemented for uks

Note: return true because this type is castable to AssociationType. Not because all collections are associations.

Return true if the implementation is castable to CollectionType. Essentially a polymorphic version of (type instanceof CollectionType.class)

A CollectionType is additionally an AssociationType; so if this method returns true, isAssociationType() should also return true.

Should the parent be considered dirty, given both the old and current value?

Should the parent be considered dirty, given both the old and current value?

Compare two instances of the class mapped by this type for persistence "equality" (equality of persistent state).

This should always equate to some form of comparison of the value's internal state. As an example, for something like a date the comparison should be based on its internal "time" state based on the specific portion it is meant to represent (timestamp, date, time).

Has the value been modified compared to the current database state? The difference between this and the isDirty(Object, Object, boolean[], SessionImplementor) methods is that here we need to account for "partially" built values. This is really only an issue with association types. For most type implementations it is enough to simply delegate to isDirty(Object, Object, boolean[], SessionImplementor) here/

Are objects of this type mutable. (With respect to the referencing object ... entities and collections are considered immutable because they manage their own internal state.)

Retrieve an instance of the mapped class from a JDBC resultset. Implementors should handle possibility of null values.

Retrieve an instance of the mapped class from a JDBC resultset. Implementations should handle possibility of null values. This method might be called if the type is known to be a single-column type.

Write an instance of the mapped class to a prepared statement. Implementors should handle possibility of null values. A multi-column type should be written to parameters starting from index.

Write an instance of the mapped class to a prepared statement, ignoring some columns. Implementors should handle possibility of null values. A multi-column type should be written to parameters starting from index.

During merge, replace the existing (target) value in the entity we are merging to with a new (original) value from the detached entity we are merging. For immutable objects, or null values, it is safe to simply return the first parameter. For mutable objects, it is safe to return a copy of the first parameter. For objects with component values, it might make sense to recursively replace component values.

Replace the elements of a collection with the elements of another collection.

Map identifiers to entities or collections. This is the second phase of 2-phase property initialization.

Given a hydrated, but unresolved value, return a value that may be used to reconstruct property-ref associations.

A representation of the value to be embedded in an XML element.

Return the JDBC types codes (per java.sql.Types) for the columns mapped by this type.

Given an instance of the type, return an array of boolean, indicating which mapped columns would be null.

A representation of the value to be embedded in a log file.

Is the primary key of the owning entity table to be used in the join?

Wrap the naked collection instance in a wrapper, or instantiate a holder. Callers MUST add the holder to the persistence context!

Get an iterator over the element set of the collection in POJO mode

Instantiate a new "underlying" collection exhibiting the same capacity charactersitcs and the passed "original".