View Revisions: Issue #926
| Summary | 0000926: Fix premature removal of personal user account | ||
|---|---|---|---|
| Revision | 2018-01-18 16:17 by rijkr | ||
| Description | IST: Logically deleted users are removed from the database when no input/output document instances are present for that user. However, when printing is charged via Delegated Print, no documents are present, but (pending) transactions are. As the user is removed, related personal accounts and transactions are unconditionally removed by cascade. This leads to errors, when a ticket print completes, and costs must be settled with the now removed personal account. SOLL: Do not remove a user when personal account transactions are present. These transactions will be removed in due time as part of the recurring clean-up process. So, when all transactions for a user are cleaned/removed, a logically deleted user will eventually be removed. |
||
| Revision | 2018-01-18 15:44 by rijkr | ||
| Description | IST: Logically deleted users are removed from the database when no input/output document instances are present for that user. However, when printing is charged via Delegated Print, no documents are present, but (pending) transactions are. As the the user is removed, related personal accounts and transactions are unconditionally removed by cascade. This leads to errors, when a ticket print completes, and costs must be settled with the now removed personal account. SOLL: Do not remove a user when personal account transactions are present. These transactions will be removed in due time as part of the recurring clean-up process. So, when all transactions for a user are cleaned/removed, a logically deleted user will eventually be removed. |
||
