#0102 Future Database Support #155
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/hottea!155
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/0102-future-database-support"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds extensible SQL generator architecture and documents future database support.
Changes:
src/hottea/sql.py— refactored to class-based architecture withSqlGeneratorABCtests/test_sql.py— 6 new tests for SQLiteGenerator and MySQLGeneratorREADME.md— new "Future Database Support" sectionArchitecture:
Backward compatible: existing
generate_insert()andgenerate_sql()functions unchanged.Closes: #0102, #0098, #0099, #0100, #0101
Audit Review — PR #155
Clean refactoring to class-based SQL generator architecture. All 4 issues (#0098-#0101) addressed. Good use of ABC, clean subclass separation (transaction syntax only), backward-compatible wrappers preserved. README documents migration path and phase-out plan clearly.
Minor note:
SqlGenerator.columnsis a mutable class attribute — consider using a tuple or defensive copy if subclass mutation is a concern. Not a blocking issue.No suggestions — clean PR.
Summary
Result: COMMENT — no issues found.
APPROVED. Clean SQL generator architecture with future DB support. Merge when ready.