Hibernate ORM - hibernate-core 6.4.4.Final · org.hibernate.event.spi.FlushEntityEvent

Field Summary

Modifier and Type	Field and Description
private boolean	allowedToReuse
private Object[]	databaseSnapshot
private boolean	dirtyCheckHandledByInterceptor
private boolean	dirtyCheckPossible
private int[]	dirtyProperties
private Object	entity
private EntityEntry	entityEntry
private boolean	hasDirtyCollection
private int	instanceGenerationId
private Object[]	propertyValues

Constructor Summary

Access	Constructor and Description
public	FlushEntityEvent(EventSource source, Object entity, EntityEntry entry)

Method Summary

Modifier and Type	Method and Description
public Object[]	getDatabaseSnapshot()
public int[]	getDirtyProperties()
public Object	getEntity()
public EntityEntry	getEntityEntry()
public int	getInstanceGenerationId()
public Object[]	getPropertyValues()
public boolean	hasDatabaseSnapshot()
public boolean	hasDirtyCollection()
public boolean	hasDirtyProperties()
public boolean	isAllowedToReuse()
public boolean	isDirtyCheckHandledByInterceptor()
public boolean	isDirtyCheckPossible()
public void	resetAndReuseEventInstance(Object same as constructor parameter entity, EntityEntry same as constructor parameter entry) This is a terrible anti-pattern, but particular circumstances call for being able to reuse the same event instance: this is otherwise allocated in hot loops and since each event is escaping the scope it's actually causing allocation issues.
public void	setAllowedToReuse(final boolean allowedToReuse)
public void	setDatabaseSnapshot(Object[] databaseSnapshot)
public void	setDirtyCheckHandledByInterceptor(boolean dirtyCheckHandledByInterceptor)
public void	setDirtyCheckPossible(boolean dirtyCheckPossible)
public void	setDirtyProperties(int[] dirtyProperties)
public void	setHasDirtyCollection(boolean hasDirtyCollection)
public void	setInstanceGenerationId(final int instanceGenerationId)
public void	setPropertyValues(Object[] propertyValues)

Inherited from org.hibernate.event.spi.AbstractEvent:: getSession

Field Detail

allowedToReuse	back to summary
private boolean allowedToReuse

databaseSnapshot	back to summary
private Object[] databaseSnapshot

dirtyCheckHandledByInterceptor	back to summary
private boolean dirtyCheckHandledByInterceptor

dirtyCheckPossible	back to summary
private boolean dirtyCheckPossible

dirtyProperties	back to summary
private int[] dirtyProperties

entity	back to summary
private Object entity

entityEntry	back to summary
private EntityEntry entityEntry

hasDirtyCollection	back to summary
private boolean hasDirtyCollection

instanceGenerationId	back to summary
private int instanceGenerationId

propertyValues	back to summary
private Object[] propertyValues

Constructor Detail

FlushEntityEvent	back to summary
public FlushEntityEvent(EventSource source, Object entity, EntityEntry entry)

Method Detail

getDatabaseSnapshot	back to summary
public Object[] getDatabaseSnapshot()

getDirtyProperties	back to summary
public int[] getDirtyProperties()

getEntity	back to summary
public Object getEntity()

getEntityEntry	back to summary
public EntityEntry getEntityEntry()

getInstanceGenerationId	back to summary
public int getInstanceGenerationId()

getPropertyValues	back to summary
public Object[] getPropertyValues()

hasDatabaseSnapshot	back to summary
public boolean hasDatabaseSnapshot()

hasDirtyCollection	back to summary
public boolean hasDirtyCollection()

hasDirtyProperties	back to summary
public boolean hasDirtyProperties()

isAllowedToReuse	back to summary
public boolean isAllowedToReuse()

isDirtyCheckHandledByInterceptor	back to summary
public boolean isDirtyCheckHandledByInterceptor()

isDirtyCheckPossible	back to summary
public boolean isDirtyCheckPossible()

resetAndReuseEventInstance	back to summary
public void resetAndReuseEventInstance(Object entity, EntityEntry entry) This is a terrible anti-pattern, but particular circumstances call for being able to reuse the same event instance: this is otherwise allocated in hot loops and since each event is escaping the scope it's actually causing allocation issues. The flush event does not appear to be used recursively so this is currently safe to do, nevertheless we add an allowedToReuse flag to ensure only instances whose purpose has completed are being reused. N.B. two out of three parameters from the constructor are reset: the same EventSource is implied on reuse. Parameters entity:Object same as constructor parameter entry:EntityEntry same as constructor parameter

resetAndReuseEventInstance

back to summary

public void resetAndReuseEventInstance(Object entity, EntityEntry entry)

This is a terrible anti-pattern, but particular circumstances call for being able to reuse the same event instance: this is otherwise allocated in hot loops and since each event is escaping the scope it's actually causing allocation issues. The flush event does not appear to be used recursively so this is currently safe to do, nevertheless we add an allowedToReuse flag to ensure only instances whose purpose has completed are being reused. N.B. two out of three parameters from the constructor are reset: the same EventSource is implied on reuse.

Parameters

entity:Object: same as constructor parameter
entry:EntityEntry: same as constructor parameter

setAllowedToReuse	back to summary
public void setAllowedToReuse(final boolean allowedToReuse)

setDatabaseSnapshot	back to summary
public void setDatabaseSnapshot(Object[] databaseSnapshot)

setDirtyCheckHandledByInterceptor	back to summary
public void setDirtyCheckHandledByInterceptor(boolean dirtyCheckHandledByInterceptor)

setDirtyCheckPossible	back to summary
public void setDirtyCheckPossible(boolean dirtyCheckPossible)

setDirtyProperties	back to summary
public void setDirtyProperties(int[] dirtyProperties)

setHasDirtyCollection	back to summary
public void setHasDirtyCollection(boolean hasDirtyCollection)

setInstanceGenerationId	back to summary
public void setInstanceGenerationId(final int instanceGenerationId)