- Is graham-campbell/database compatible with Laravel 10 or Laravel 11?
- No. The package is tied to Laravel 4.2, which reached end of life in 2015, and its container bindings, Eloquent APIs, and autoloading conventions are from that era. It is not a dependency for modern Laravel applications.
- Is graham-campbell/database abandoned?
- Yes. It is published under the GrahamDeprecated organization, has a single tagged release (v0.1.4-alpha), and has zero dependents. That namespace is an explicit archival signal, so you should treat it as unmaintained.
- What does the Laravel Database package actually do?
- It provides a thin repository/CRUD wrapper over Laravel's Eloquent and query builder, with service provider and facade integration. It is described asa config-driven database layer, but its scope is small and specific to Laravel 4.2. It is not a full database abstraction or a replacement for Laravel's native database features.
- How do I install graham-campbell/database with Composer?
- You generally should not install it for a maintained application. In a frozen Laravel 4.2 context, Composer constraints would likely require an explicit alpha version such as 0.1.4-alpha and possibly minimum-stability settings. Modern dependency graphs will reject its PHP 5.x-era constraints.
- Can I use this package in production?
- No, not in any maintained system. The only technical fit is an application already frozen on Laravel 4.2, and even then the framework itself is the real constraint and remediation item. For production work, use Laravel's native database layer or a maintained repository package.
- Does it support multiple database connections?
- The package is presented as config-driven and able to work alongside Laravel's database layer, including multiple connections in its blurb. However, any connection behavior would depend on Laravel 4.2's native database configuration rather than modern Laravel features. Do not rely on the package for new multi-connection architecture.
- How does it integrate with Eloquent and the query builder?
- It wraps Eloquent and the query builder in a repository-style layer intended to encapsulate common operations such as find, create, update, delete, paginate, and cache-aware reads. The integration is implemented for Laravel 4.2 APIs, not current Eloquent. You can borrow the pattern, but not the implementation.
- Is the package tested and actively maintained?
- There is no evidence of active maintenance: it has one alpha release and lives under GrahamDeprecated with zero dependents. The technical assessment notes no issue triage and an archival namespace. Treat it as prior art rather than a supported dependency.
- What are good alternatives to graham-campbell/database?
- Use Laravel's built-in Eloquent models, query builder, and database configuration first. If you want repository/CRUD abstractions, choose a maintained package compatible with your Laravel version or write a small base repository in your application. For Laravel 4.2 systems, the real alternative is planning a framework upgrade.
- Can I reuse the repository pattern from this package?
- Yes, the architectural idea is generic and portable: a base repository class that encapsulates find, create, update, delete, paginate, and cache-aware reads. The implementation is bound to Laravel 4.2, so reimplement the pattern against current Laravel APIs. Review the source as prior art, not as a drop-in dependency.