Weave Code
Filament Database Laravel Package
crumbls/filament-database
A Laravel Filament package for working with your database inside the admin panel. Browse tables and records, inspect schema details, and manage data without leaving Filament.
A Filament 5+ database browser that emulates PhpMyAdmin, but for other systems. Built for with love for Laravel.
Frequently asked questions about Filament Database
- What is crumbls/filament-database and what does it do in Laravel?
- It is a Filament 5+ package that adds an in-app database workspace inside the Filament admin panel. It lets developers browse tables and records, inspect schema details, use a SQL workspace, and access grouped schema, transfer, and destructive actions. It is designed to emulate a phpMyAdmin-style workflow for Laravel applications rather than act as a thin query tool.
- How do I install and configure crumbls/filament-database in a Laravel Filament app?
- You need a Laravel application with Filament as the admin layer and at least one reachable relational database connection. The main integration work is config publication plus authorization and connection scoping policies. The package is config-driven, with options such as max_export_rows and driver-aware controls, so tune it rather than forking it. Check the README for exact install commands and published config details.
- Does crumbls/filament-database support Laravel 11, Laravel 12, and Filament 5?
- The package is described as built for Laravel and requires Filament 5+. The provided context does not list exact PHP, Laravel, and Filament version constraints, so verify composer.json and the README before upgrading. Also note that 3.1.0 includes behavioral changes, so it should not be treated as a purely additive drop-in update.
- Is crumbls/filament-database safe to use in production?
- It fits internal or back-office Laravel deployments where Filament is already the admin layer, but it is a poor fit for customer-facing or multi-tenant apps unless authorization and connection scoping are wrapped tightly. It places a high-privilege database surface inside the Laravel app boundary, sharing auth, sessions, and deployment lifecycle. Read-only enforcement is driver-conditional, export truncation may affect reconciliation data, and application-level audit logging is not verified. Confirm the production lockfile and policies independently before relying on it.
- How does the 10,000-row export limit work and can I change it?
- The package exposes a max_export_rows setting and uses a 10,000-row default cap. You can tune it through configuration, but the context does not verify whether truncation is shown in the UI, returned in metadata, or logged. It also does not clarify whether the cap is a query-level limit or a post-fetch slice. Treat large exports as potentially incomplete for audit or reconciliation unless you verify the behavior.
- Why does my CSV export alter values that look like spreadsheet formulas?
- The package neutralizes CSV formula injection by prefixing formula-like cells, which protects against spreadsheet injection but breaks exact round-trip fidelity. Any downstream consumer treating CSV exports as a system of record may see altered values. Use JSON or SQL exports when exact data reproduction matters.
- Is the SQL runner read-only, and which database drivers enforce it?
- Read-only SQL relies on database-level read-only controls on supported drivers, with server-side timeouts only on PostgreSQL, MySQL, and MariaDB. On other drivers or misconfigured connections, the guardrail may be weaker than the UI implies. The context does not document the fallback for unsupported drivers, so verify enforcement before exposing the SQL workspace.
- Why is the SQL workspace disabled when table visibility restrictions are configured?
- Disabling the SQL runner whenever table visibility restrictions are set is a safe default, but it silently removes a feature from deployments that previously relied on it. The context lists whether this is global or per-panel/per-connection as a key open question. Check the package configuration and treat this as a behavior change for affected users rather than a purely additive feature.
- Does crumbls/filament-database write SQL executions and destructive actions to an audit log?
- The context confirms package-internal history and notes that per-connection history scoping changes existing workflows. It does not verify whether SQL executions, exports, schema actions, or destructive actions are written to an application audit log with actor identity. For compliance or incident review, integrate application-level auditing or confirm the package behavior first.
- What are alternatives to crumbls/filament-database for browsing databases in Laravel?
- Alternatives include external tools such as phpMyAdmin, Adminer, TablePlus, or DataGrip, as well as Laravel Nova tools, custom Filament resources, or other Filament database browser packages. This package's differentiator is a phpMyAdmin-like workspace inside Filament with config-driven controls. Compare alternatives on authorization, read-only enforcement, export fidelity, and audit logging.
Weaver
How can I help you explore Laravel packages today?