- What is mindy/query_builder and what databases does it support?
- mindy/query_builder is a lightweight, fluent query builder for PHP that supports SQLite, MySQL, and PostgreSQL. It uses a Django-like, chainable syntax for selects, joins, where conditions, ordering, and limits. It is a standalone utility from the MindyPHP ecosystem, not a Laravel component.
- Does mindy/query_builder work with Laravel?
- There is no evidence of a Laravel service provider, facade, configuration file, or container integration. Laravel already ships its own query builder and Eloquent, so mindy/query_builder does not fill a framework gap. Using it in Laravel would require manual wiring and compatibility testing.
- How do I install mindy/query_builder with Composer?
- You can attempt installation with Composer using the package name mindy/query_builder. However, the last release was in February 2018 and Laravel integration is not documented. Treat installation as unproven until you validate autoloading and runtime behavior in a sandbox.
- Is mindy/query_builder compatible with PHP 8 and modern Laravel versions?
- The package dates from the PHP 5.6/7.x era and has no visible validation for PHP 8.1 or 8.2, which modern Laravel requires. Compatibility with current Laravel versions is unproven and should be assumed broken until a proof of concept passes. Test PDO behavior, prepared statements, and SQL dialect support before relying on it.
- Does mindy/query_builder use parameter binding to prevent SQL injection?
- The package is described as safely parameterized, and parameter binding is expected for values in its fluent API. Still, you should review the source and run a security review before production use because the project is unmaintained. Confirm that every value path uses bound parameters and that identifiers are handled separately.
- How does mindy/query_builder compare to Laravel's Illuminate\Database query builder?
- Laravel's Illuminate\Database query builder is maintained, documented, framework-integrated, and covers the same select, join, where, order, and limit operations. mindy/query_builder is a standalone alternative with a Django-like syntax but no Laravel ecosystem support. For Laravel work, the native builder is the lower-risk choice.
- Can I use mindy/query_builder in a new Laravel project?
- It is not recommended for a new Laravel project. The package has no native Laravel integration, low ecosystem validation, and no active maintenance. Use Laravel's native query builder or Eloquent unless you have a legacy MindyPHP requirement.
- Is mindy/query_builder still maintained?
- No. The last release was 2018-02-05, and the repository has 0 stars and 0 dependents. There is no visible active maintenance, vendor support, or community. If you adopt it, your team effectively owns patching and PHP upgrades.
- What are the risks of using mindy/query_builder in production?
- The main risks are abandoned dependency exposure, unpatched security issues, PHP-version incompatibility, and behavioral differences from Laravel's query builder. Production use also creates long-term maintenance cost because you must handle security fixes and compatibility work yourself. Isolate it behind an adapter and have an exit plan if you must keep it.
- How do I migrate from mindy/query_builder to Laravel's native query builder?
- Inventory every query, map each one to Laravel's query builder or Eloquent, and introduce a repository or adapter interface around legacy calls. Replace queries incrementally by domain or endpoint with contract tests and dual-run comparisons where feasible. Avoid a big-bang migration and remove the dependency once parity is proven.