When a PERSIST cascade hits an uninitialized PersistentCollection (PC) on a lazy property, the PC always gets initialized.
This happens even if there are no 'queued actions' associated with the PC.
This seems unnecessary since no potential changes may have been performed on the uninitialized PC or the unloaded Elements.
We noticed this when hunting down superflous SELECT-Statements in the context of performance issues.
Testcase and possible solution will be attached soon
originally noticed in hibernate 3.51 with postgresql
reproduced with hibernate 5 git master at 2017-07-30 on h2-DB