graham-campbell/database
A Laravel database package from Graham Campbell that provides a streamlined, configurable database layer with multiple connections and seamless integration with Laravel's query builder and Eloquent for simple, consistent data access.
What this package is, in TPM terms. A small, abandoned Laravel extension from the Graham Campbell ecosystem, published under the GrahamDeprecated organization with a single tagged release (v0.1.4-alpha) and zero dependents. Its stated purpose — "Some Extra Database Stuff For Laravel 4.2" — is a thin repository/CRUD wrapper over Eloquent and the query builder. For a TPM, the relevant question is not "does it work?" but "is there any decision this package can legitimately inform or accelerate?" The honest answer: only as prior art, never as a dependency.
Architecture fit. Effectively zero for any maintained system. Laravel 4.2 reached end of life in 2015; the package is bound to that era's container bindings, Eloquent APIs, and autoloading conventions. The idea (a base repository class encapsulating find/create/update/delete/paginate and cache-aware reads) is architecturally generic and portable, but the implementation is not. In the one context where it technically "fits" — an application frozen on Laravel 4.2 — the framework, not this package, is the real constraint and the real remediation item.
Integration feasibility. Low, with three compounding blockers. (1) Composer constraints will pin PHP to the 5.x era and reject resolution alongside any modern dependency graph; installing even in a legacy context likely requires minimum-stability: dev or an explicit @alpha flag. (2) The GrahamDeprecated namespace is an explicit archival signal — no issue triage,
How can I help you explore Laravel packages today?