From 0cdbfa671f4a43044fd63dee5bf05d520021dc15 Mon Sep 17 00:00:00 2001 From: Murilo Rosa Date: Wed, 6 Mar 2024 14:39:53 +0000 Subject: [PATCH] lint notes --- development_notebook/2024-03-05.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/development_notebook/2024-03-05.md b/development_notebook/2024-03-05.md index 52521de..c9fb108 100644 --- a/development_notebook/2024-03-05.md +++ b/development_notebook/2024-03-05.md @@ -8,7 +8,7 @@ These models have admin defined and tested for them, but they dont have any func # Today -Add functionality for accounts to have the current balance. +Add functionality for accounts to have the current balance. Simply add save on transactions to add their ammounts to or the delta of their amount to the account. These need to account for all possible relevant field changes, as well as delete. @@ -18,7 +18,7 @@ Keep balance in Account updated. ## Brute Force solution -Get balance by function, which calculates at call from all transactions. +Get balance by function, which calculates at call from all transactions. ## Improved solution @@ -32,7 +32,7 @@ Problem: We still need to deal with (1.) changing transaction's account and (2.) Solutions: -1. Simply prevent changing. We may give this feature to the user, but delete the transaction and create another on the different account. +1. Simply prevent changing. We may give this feature to the user, but delete the transaction and create another on the different account. (Can we do this at DB level (prevent a change)? In [[Future Improvements]] we might want to do this all in DB level.) 2. Deletion should not be a problem. Since we are already using soft delete, we can use this to calculate the balance and then actually delete.