Refactor SQLAlchemy Repository for Multiple Tables

[migduroli]

Summary

Our current SQLAlchemy repository module, represented by the SQLAlchemyRepository class, is designed to handle operations on a single table and includes standard CRUDLDel methods. However, as our application grows, we find the need to work with multiple tables in a more organized and modular way.

Motivation

1. Modularity: The current design limits our ability to manage multiple tables efficiently. We want to refactor our repository structure to promote better code modularity and separation of concerns.

2. Code Reusability: To enhance code reusability, we propose creating a new class called SQLAlchemyTableManager, responsible for encapsulating the CRUDLD (Create, Retrieve, Update, Delete, List, Drop) methods for a specific table.

3. Improved Testing: By refactoring our repository structure, we can make our tests more granular and specific, which can help in maintaining and expanding our codebase.

Proposed Changes

1. Introduce a new class, SQLAlchemyTableManager, which encapsulates CRUDLDel methods for a specific table.

2. Create a new class, SQLAlchemyTableRepository, that inherits from SQLAlchemyRepository and uses SQLAlchemyTableManager to handle operations on a specific table.

3. Update import statements in the codebase to reflect the use of SQLAlchemyTableRepository where necessary.

4. Modify tests to work seamlessly with the new repository structure.

Impact

• Improved code organization and separation of concerns.
• Enhanced modularity for working with multiple tables.
• Updated import statements in the codebase.
• Modifications to tests to accommodate the new repository structure.