Table Data Gateway pattern

Description:

The Table Data Gateway pattern provides a way to encapsulate all the SQL operations for a single table or view within a gateway class. This pattern allows for a single point of access to the data in a table, ensuring a clean separation between the database and the application logic. The key elements of the Table Data Gateway pattern include:

• Gateway Class: Encapsulates the database access logic for a specific table or view.
• CRUD Operations: Methods for Create, Read, Update, and Delete operations.
• Separation of Concerns: Decouples the SQL queries from the application logic, promoting single responsibility and easier maintenance.
• Reusability: Reusable and testable components that centralize data access logic.

References:

1. Martin Fowler's Table Data Gateway: https://www.martinfowler.com/eaaCatalog/tableDataGateway.html
2. Wikipedia: Table Data Gateway: https://en.wikipedia.org/wiki/Table_data_gateway
3. Source Code Examples: Table Data Gateway: https://www.sourcecodeexamples.net/2018/04/table-data-gateway.html
4. P of EAA

Acceptance Criteria:

1. Implement a gateway class that encapsulates SQL operations for a specific table.
2. Include methods for Create, Read, Update, and Delete operations within the gateway class.
3. Ensure that the gateway class is well-documented and includes unit tests to verify its functionality.

The issue names no files, tests, or entry points. Start by reviewing the repository's existing design-pattern implementations and database-related examples, then determine the table or view and API needed to satisfy the CRUD, documentation, and unit-test acceptance criteria.