User Story #233 (closed)
Opened 13 years ago
Closed 13 years ago
Read/write separation is not clean enough
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 3.0-M3 |
| Component: | ORM | Keywords: | spring,hibernate,flush,interceptor,read,write, iteration4 |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
All service methods are marked as read or write, however there are times when "write-like" actions take place which can cause difficulties. An example is in PojosImpl where we'd like to re-arrange results before returning them to the user.
Read calls should be protected from accidental writes to the db through AOP/interceptor magic. Currently, the Spring wrappers around Hibernate sessions tend to want to guarantee flushes.
We need a flag to guarantee non-flush.
Change History (2)
comment:1 Changed 13 years ago by jmoore
comment:2 Changed 13 years ago by jmoore
- Keywords iteration4 added
- Milestone changed from Unscheduled to 3.0-M3
- Resolution set to duplicate
- Status changed from new to closed
Later ticket #323 subsumes this one. Closing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Depends on #236