fix: improve exception handling in database connection

[riyagoyal01]

Fixes #1102

What this PR does

This PR improves error handling in the get_db_connection context manager by catching database-specific exceptions and adding structured logging.

Changes made

• Replaced generic except Exception with except sqlite3.Error to handle database-related errors explicitly
• Added logging using logger.exception() for better debugging and traceability
• Ensured transactions are rolled back safely on database failures
• Preserved existing behavior of re-raising the exception after rollback
• No change to connection lifecycle (commit, rollback, close logic remains intact)

Why this change is needed

Previously, the code used a generic except Exception block, which:

• Could hide the nature of database-related failures
• Made debugging harder due to lack of logging
• Did not distinguish SQLite errors from other runtime issues

Using sqlite3.Error with logging makes error handling:

• More precise
• Easier to debug
• More aligned with best practices

Tested

• Verified that database connection still commits on success
• Verified rollback and logging on simulated database errors
• No breaking changes introduced

Summary by CodeRabbit

• Bug Fixes
  • Enhanced database connection error handling with improved exception detection, error logging, and connection cleanup to ensure more reliable database operations.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds module-level logging setup and refines error handling in the database connection module to catch sqlite3.Error specifically instead of broad exceptions, with added logging and proper connection cleanup in the finally block.

Changes

Cohort / File(s)	Summary
Database Error Handling backend/app/database/connection.py	Added module-level logger initialization and improved exception handling to catch sqlite3.Error specifically instead of broad Exception. Includes logging of database errors and ensures connections are properly closed in finally block.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A logger hops through SQLite's door,
Catching errors with precision, not before,
No broad exceptions to confuse the way,
Just sqlite3.Error saves the day!
Connection closed, transactions clear,
Better debugging, crystal-lear! 🔍✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately summarizes the main change: improving exception handling in the database connection module as per the linked issue requirements.
Linked Issues check	✅ Passed	All objectives from issue #1102 are met: replaced broad Exception with sqlite3.Error, added logging via logger.exception(), preserved rollback and re-raise behavior.
Out of Scope Changes check	✅ Passed	All changes directly address the objectives specified in issue #1102; no out-of-scope modifications detected in the database connection error handling.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}