Active Record pattern

[iluwatar]

Description

The Active Record design pattern is a common architectural pattern used to manage database records. It simplifies data access by encapsulating the database logic within a model class. Each instance of the model corresponds to a row in the database, and the model class includes methods for CRUD (Create, Read, Update, Delete) operations.

Main Elements of Active Record Pattern:

1. Model Class: Represents a table in the database. Each instance represents a single row.
2. CRUD Operations: Methods for Create, Read, Update, and Delete operations are defined within the model.
3. Database Connection: The model class manages the database connection.
4. Simple Queries: Basic querying capabilities are encapsulated within the model.

References

• Active Record Pattern - Martin Fowler
• Java Design Patterns Project Contribution Guidelines
• Active Record Wikipedia

Acceptance Criteria

1. A new model class should be created, representing a database table.
2. The model class should include methods for basic CRUD operations.
3. The implementation should adhere to the project’s contribution guidelines and include relevant documentation and unit tests.

[stephen-lazarionok]

I may help with implementing this pattern. Please let me know if it's oaky with you.

[iluwatar]

Sure, go ahead, your contribution is welcome!

[stephen-lazarionok]

Okay, I will work on this pattern

[stephen-lazarionok]

Pull request #206 is prepared. Please review.

[stephen-lazarionok]

I've fixed the points raised and left my comments

[iluwatar]

jOOQ uses Active Record pattern: http://www.jooq.org/

[iluwatar]

Described in book "Patterns of Enterprise Application Architecture" by Fowler

[iluwatar]

https://www.vertabelo.com/blog/orms-under-the-hood/

[TwentyVentti]

@iluwatar I can help work on this pattern let me know if that’s okay with you.

[iluwatar]

Nice, please go ahead @TwentyVentti

[iluwatar]

Updated task description

[ipaulaandreea]

@iluwatar Can you assign me with this task, please?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.