Skip to main content
Software Engineering

Return to Answer

Add a comma. Fix dead link (404). Reference: https://web.archive.org/web/20240601000000*/https://www.nichesoftware.co.nz/blog/2011-05/494/reconsidering-repository-pattern
Source Link
edit approved Mar 25 at 21:30
Pang
edit approved Mar 25 at 21:30
Pang
  • 335
  • 5
  • 8

In theory, I think it makes sense to encapsulate the database connection logic to make it more easily reusable, but as the link below argues, our modern frameworks essentially take care of this now.

Reconsidering the Repository PatternReconsidering the Repository Pattern

In theory I think it makes sense to encapsulate the database connection logic to make it more easily reusable, but as the link below argues, our modern frameworks essentially take care of this now.

Reconsidering the Repository Pattern

In theory, I think it makes sense to encapsulate the database connection logic to make it more easily reusable, but as the link below argues, our modern frameworks essentially take care of this now.

Reconsidering the Repository Pattern

Post Migrated Here from stackoverflow.com (revisions)
Source Link
Splendor
Splendor
  • 251
  • 1
  • 4

In theory I think it makes sense to encapsulate the database connection logic to make it more easily reusable, but as the link below argues, our modern frameworks essentially take care of this now.

Reconsidering the Repository Pattern