Task #141 (closed)
Opened 18 years ago
Closed 18 years ago
UpdateFilter/merge should handle contents of CurrentDetails differently.
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M3 |
| Component: | Security | Version: | 3.0-M1 |
| Keywords: | iteration2,details,merge,hibernate,filter | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently all the checks that take place on the entities in a graph are also applied to the owner, group, and event fields of Details where it's been updated in the same filtering step.
This should be prevented. Perhaps the GraphHolder? of those Experimenter, ExperimenterGroup?, and Event should distinguish them.
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from Unscheduled to cycle2
comment:2 Changed 18 years ago by jmoore
- Keywords iteration2 added
comment:3 Changed 18 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r828 significantly reworks how UpdateFilter works. In fact, most of the functionality from UpdateFilter has been pushed into MergeEventListener. UpdateFilter is no longer responsible for reloading and only for keeping multiple calls to session.merge() in sync (see #143). Instead, MergeEventListener which doesn't have to constantly make calls to IQuery is able to more efficiently reload details. (It relies on some internal Hibernate APIs but we'll track those.) With this, there should be no problems of CurrentDetails types being unloaded.