ticketorder and arrival deletes tickets in different ways
Bug #725456 reported by
Mathias Bøhn Grytemark
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| lancms | ||||||
| Lancms1 |
New
|
Undecided
|
Unassigned | |||
Bug Description
It seems ticketorder does a DELETE on the ticket-row, while arrival does UPDATE with "set status='deleted'".
This screws up the ticketadmin overview and listTickets because it doesn't look for status!='deleted'.
Revision history for this message
| Thomas Presthus (tpresthus) wrote | #1 |
| no longer affects: | lancms |
To post a comment you must log in.
I think it could save some time and confusion to separate some logic (like knowing what makes a ticket deleted) into a layer of it's own, sitting between the database and the views.
I'm not proposing adding a full blown MVC-based approach or anything, but merely collecting business logic that's used across different modules (ticketorder and ticketadmin in this case - maybe also arrival) in a single source of truth.