Change: SQLite cache backend should be DBI backend

Problem Statement

The current SQLite cache backend class is limited to SQLite, which restricts its applicability and flexibility. To enhance the utility of the cache backend, it should be converted into a generic database backend that leverages the existing DBI (database interface) classes of Hazaar MVC.

Who will benefit?

Developers and users of the Hazaar MVC framework who require a flexible and extensible caching mechanism that can interface with various database systems.

Benefits and risks

Benefits

• Increases the flexibility of the caching mechanism by supporting multiple database types.
• Leverages the existing DBI classes, ensuring consistency and reducing redundant code.
• Enhances the scalability and adaptability of applications built on Hazaar MVC.

Risks

• Potential complexity in refactoring the existing code to integrate with DBI classes.
• Requires thorough testing to ensure compatibility and stability across different database systems.
• Updates to documentation and potential retraining for developers using the new backend.

Proposed solution

Refactor the current SQLite cache backend class to extend and utilize the existing DBI classes in Hazaar MVC. This involves:

1. Abstracting the database-specific logic into a generic database backend class.
2. Implementing methods to interface with different database systems using the DBI classes.
3. Ensuring that the new backend maintains compatibility with the existing cache interface.

Examples

N/A

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)