Add defence from model listener polluting hibernate session 1st level cache

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.0 CE M3
• Fix Version/s: 6.2.0 CE M2
• Component/s: Core Infrastructure, Core Infrastructure > ORM
• Labels: None
• Similar Issues: Show 5 results ; ;

  LPS-21928	Parent category needs to be cleared from Hibernate Session Cache(first level cache) during categories hierarchy building
  LPS-31856	Automatically sync up Hibernate session state on nesting transaction creation
  LPS-52219	As a developer, I'd like to provide a programming way for long running tx to manually sync hibernate session states with DB in order to prevent session's 1st level cache from building up
  LPS-21594	Hibernate Session Cache(first level cache) needs to be cleared after saving Blob
  LPS-16459	Add cache listeners

This fix prevents improper model listeners from polluting hibernate session 1st level cache.
However to achieve this goal we will have to sacrifice's hibernate's uniqueness checking feature, this will cause us losing the concurrent modification detection.

But this is a necessary evil to do, without this fix, a bad model listener will cause tricky uniqueness checking failure, it is very hard to locate the root cause,

We suppose to define a batch of rules for what model listeners can do, what they can not do. Once we rule all model listeners' behaviors, it is better to add back the hibernate's uniqueness checking.

[Tammy Fong]

Committed on:
Portal 6.2.x GIT ID: b52c38824c2f6875d67267beef7e8c337ecc5c11.