Feature: SQLite backend for DBI

Problem Statement

The Hazaar DBI component currently lacks support for SQLite as a backend. SQLite is a lightweight, file-based database engine that is widely used for development, testing, and small-scale production applications. Adding support for SQLite would increase the versatility and adoption of the Hazaar DBI component.

Who will benefit?

• Developers using Hazaar for projects where SQLite is sufficient or preferable.
• Teams looking for a simple, zero-configuration database solution for testing or small applications.
• Applications requiring an embedded database without the overhead of a full database server.

Benefits and risks

Benefits

• Provides an additional database option for developers, enhancing flexibility.
• Makes Hazaar DBI more versatile and suitable for smaller projects or embedded systems.
• Facilitates easier testing and development workflows with SQLite's minimal setup.

Risks

• Adding SQLite support may introduce additional maintenance overhead for the DBI component.
• Differences in feature sets between SQLite and other databases (e.g., MySQL, PostgreSQL) could lead to inconsistencies in functionality or compatibility.

Proposed solution

1. Implement a new SQLite backend for the Hazaar DBI component.
2. Ensure the backend supports core DBI functionality, including schema management, queries, and transactions.
3. Add test cases to validate SQLite support, ensuring compatibility with existing DBI features.
4. Update documentation to include instructions for using the SQLite backend and any SQLite-specific considerations.

Priority/Severity

• High (This will bring a huge increase in performance/productivity/usability/legislative cover)
• Medium (This will bring a good increase in performance/productivity/usability)
• Low (anything else e.g., trivial, minor improvements)