Bug #322 (closed)
Eviction in destructive sections of PojosImpl code is lazily loading.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Cc: | |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
#318/r908 re-enacts the PojoOptions?.isGroup() code. IPojos.findContainerHierarchies(), however, is failing its tests because objects which failed the filter are being lazily loaded. It should be possible to disable Hibernate events to prevent this from happening.
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Priority changed from critical to minor
comment:2 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Rather than deleting this ticket, closing and directing interested parties to #323.
comment:3 Changed 18 years ago by jmoore
- Keywords changed from lazyload, hibernate to lazyload, hibernate, iteration4
Moving to proper iteration (4)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Not true. It was the new session.isDirty() call in the readOnly service cleanup block of EventHandler which was making extra calls. I had already implemented the disabling functionality anyway (not committed); it may be useful in the future. We should also look at setting FlushMode to never on the readOnly methods. #318 is now passing (will check in momentarily) and so I'm lowering the priority.