An expense tracker should store decimal money carefully, use explicit dates and support totals by category without SQL injection.
What You Will Learn
This lesson focuses on Build a CLI Expense Tracker with SQLite. You will connect the operation to a concrete input, inspect the result and identify the situation in which a different approach would be safer or clearer.
Database programs need to preserve relationships, validity and durability across separate operations. SQL statements are only one part of this design: transactions, constraints and resource lifetime determine whether the stored data stays consistent.
How It Works
Create schema constraints before accepting data, bind values as parameters and check affected rows. Treat missing results, duplicate keys and lock errors as distinct situations with different remedies.
Database examples use SQLite and parameterized statements. A successful with connection: transaction block does not itself close the Connection; use close() or contextlib.closing() when finished.
Worked Example
The following example isolates the main behavior so you can run it from a local Python installation. Read the inputs first, then follow the operation and the final printed result.
import sqlite3
from decimal import Decimal
with sqlite3.connect(":memory:") as db:
db.execute("CREATE TABLE expenses (category TEXT, cents INTEGER)")
db.executemany("INSERT INTO expenses VALUES (?, ?)", [("food", 1250), ("travel", 400)])
cents = db.execute("SELECT SUM(cents) FROM expenses").fetchone()[0]
print(Decimal(cents) / 100)Understanding the Example
Start with the setup and import statements; these define the objects that the operation needs. Follow each assignment or function call in order, noting which arguments are provided and whether the operation creates a new value, changes existing state or returns a result. Finally, inspect the printed value or assertion rather than assuming that the operation worked.
The important behavior demonstrated here is: An expense tracker should store decimal money carefully, use explicit dates and support totals by category without SQL injection. The example uses deliberately small values so the intermediate result is easy to reason about. A larger application must still handle validation, errors and resource cleanup.
Environment note: this example may require a separately installed package, local service, platform permission or network connection. Set up the indicated environment before running it; it has not been executed automatically for this guide.
When to Use This Approach
SQLite is an effective local teaching database; use a server database when deployment requires independently connected users, centralized administration or greater concurrent write capacity.
Important Behavior and Edge Cases
Storing money as approximate binary floats and later expecting exact totals.
A connection context does not necessarily close the connection. Define transaction ownership clearly, choose bounded lock waits and keep credentials out of source and diagnostic messages.
Practice Exercise
Add a date column and a parameterized category filter.
Before running your modified code, predict the output or expected failure. Confirm the result using at least one ordinary case and one invalid, missing or boundary input. If the operation accesses external resources, first exercise it against a controlled local or test environment.
Common Beginner Mistakes
- Storing money as approximate binary floats and later expecting exact totals.
- A connection context does not necessarily close the connection. Define transaction ownership clearly, choose bounded lock waits and keep credentials out of source and diagnostic messages.
Key Takeaways
- An expense tracker should store decimal money carefully, use explicit dates and support totals by category without SQL injection.
- Choose this technique for the problem it solves, but validate inputs and follow the cleanup and failure behavior shown above.
- Next practice step: Add a date column and a parameterized category filter.