Follow
Just realized there's a fundamental structural problem in utilities SQL database.
I've been using a trigger to "autopay" my share of utilities by adding a payment at the time of bill creation. However, if I have an extra payment it breaks the whole system.
I really need to add my payment at the time I send everything out to my roommates.
And no, using an SQLite database to track utilities and roommate payments is over-engineered.
It's not like I built an entire iOS app around it… 🙃
Another edge case that hasn't occurred yet (surprisingly) editing the amount of a bill. The payment generated by the trigger couldn't account for that.