Download the PHP package sridhar-s-subramanian/filament-dbview without Composer

Filament DB View

An Adminer-like, read-only database viewer for Filament panels. By default it is scoped to your app's Eloquent models and gives you two ways to explore data:

• Database Browser — pick any model-backed table and browse it with Filament's native table (search, sort, per-column filters, pagination), a full-record slide-over, and one-click relationship previews via detected foreign keys.
• Query Runner — run ad-hoc SELECT queries in an Adminer-style console, with EXPLAIN / EXPLAIN ANALYZE, a table structure view (columns, indexes, foreign keys), CSV/JSON export, saved queries, and optional per-user query history (feature opt-in; table migration ships with the package).

By default the viewer is scoped to Eloquent models your app discovers. The Query Runner can optionally list every table on an allowed connection (->allTables()) so you can run SELECTs without a model — see Query Runner scope.

AI assistants / agents: start with AGENTS.md for a configuration checklist (install, defaults, gates, audit, production). This README has the full narrative docs.

Requirements

• PHP 8.2+
• Laravel 11, 12, or 13
• Filament v4 or v5

Installation

Register the plugin on your panel:

The migrations create two package tables (both ship by default):

• dbview_saved_queries — saved Query Runner snippets (feature on by default)
• dbview_query_history — storage for per-user query history

History writes and UI are opt-in (features.history defaults to false) so the table does not grow unbounded on busy panels. The table may still be empty after migrate until you enable the feature:

PSR-3 audit logging always runs, whether or not history is enabled.

Features

Database Browser

A point-and-click browser for one model-backed table at a time — no SQL required:

• Filament's native table with search, click-to-sort, column show/hide (remembered per table), and pagination.
• Adminer-style filters auto-derived from each column's type (text / number / date / boolean), combinable with AND/OR groups.
• Row detail slide-over showing the full record with long/JSON values expanded.
• Relationship previews — one action per foreign key (→ Related) opens the related rows in a modal, so you can follow relationships without writing joins.
• A bookmarkable ?table= URL, so a table can be linked or shared.

Query Runner

An Adminer-style console for SQL-literate users:

• Run a single read-only SELECT / WITH … SELECT. Results render in an ad-hoc grid with a row-detail slide-over. Press ⌘/Ctrl + Enter to run.
• EXPLAIN and EXPLAIN ANALYZE — inspect a query's plan. You never type EXPLAIN; the typed SELECT passes the same read-only guards and only then is a driver-appropriate prefix prepended, so the analysed statement is always a single SELECT. EXPLAIN ANALYZE executes the query to collect real timings, still row-capped, timed out, and rolled back.
• Show structure — header Structure uses the table referenced in your SQL (first real table if several; CTEs ignored). Sidebar icons still open structure for any listed table without writing a query. Shows columns, indexes, and foreign keys, Adminer-style.
• Export results to CSV or JSON (on by default; disable with features.export => false, or restrict with authorization.export_gate), saved queries, and optional per-user query history (feature off by default; enable with ->history()).
• A searchable table sidebar — click a table name to insert it into the editor, the structure icon to inspect it, or the browse link to open it in the Database Browser.

Moving between the two

The two tools are cross-linked so a table flows from one lens to the other without retyping:

• Runner → Browser: model-backed tables in the Runner sidebar have a Browse link that opens them in the Database Browser.
• Browser → Runner: the Browser's Query and Structure header actions open the Query Runner with the current table prefilled (SELECT * FROM <table>) or on its structure view.

Query Runner scope

The Database Browser is always limited to model-backed tables.

The Query Runner defaults to the same (scope = models), but can be widened so operators can run SELECTs against any real table on an allowed connection — including tables that have no Eloquent model. That is intentional: use it when you need Adminer-style ad-hoc reads beyond the model map.

Details:

• ->allTables() is shorthand for ->queryRunnerScope('connection').
• The deny list is empty by default so model-less tables are fully reachable when you opt into connection scope. Add ->denyTables([...]) only when you want exceptions (e.g. token/session tables).
• Read-only guards, redaction, row limits, timeouts, connection allowlisting, and the optional read-only DB remap still apply to every table.
• Fluent plugin setters take precedence over the query_runner values in the config file.

Query history is off by default (the dbview_query_history migration still ships). Enable the feature with ->history() or features.history => true when you want the Query Runner to persist and re-load per-user queries. PSR-3 audit logging is separate and always runs — see Auditing.

Model discovery & registry cache

The package scans your app for concrete Eloquent models and builds a registry (model → table → connection → columns / FKs). That registry is the default table allowlist for:

• the Database Browser (always), and
• the Query Runner when query_runner.scope is models (the default).

With ->allTables() / scope = connection, the Runner can also list other real tables on the connection; discovery still drives the Browser and model-backed labels/links. Per-user table_gate filters the registry further when set (see Authorization).

Configuration knobs

Exclude vs table_gate vs allTables

Cache & deploys

With cache enabled (default), the registry is stored for ttl seconds. After you:

• add/remove/rename models,
• change a model’s $table or connection,
• or change models.paths / exclude,

run:

Add that command to your deploy script when registry cache is on in production, so new models show up immediately instead of waiting for TTL.

For local development you can disable the cache:

Abstract models, interfaces, and classes that are not subclasses of Illuminate\Database\Eloquent\Model are ignored. Models whose table/connection cannot be introspected are skipped (not fatal).

Auditing

Every Query Runner attempt (allowed or denied) is written as a structured PSR-3 log line for accountability. This is always on and independent of query history.

Typical log context:

Configuration

Example dedicated channel in config/logging.php (host app):

Then:

Operational notes

• Full SQL may include secrets typed into WHERE clauses (passwords, tokens, PII). Treat the audit log (and history, if enabled) as sensitive.
• Use a restricted channel and retention policy when logs leave the app server (SIEM, CloudWatch, etc.).
• Setting log_sql => false does not disable auditing — only the SQL field is omitted. Denied attempts still log reason, user, and connection.
• Query history (when enabled) still stores full SQL so users can re-load past queries in the UI; turn history off if you do not want SQL in the database.

Authorization (opt-in)

Access is allow by default for anyone who can open your Filament panel. This package does not ship a roles system and does not depend on Spatie Permission, Filament Shield, Bouncer, or similar. Panel login is enough unless you opt in to extra checks.

To restrict by role or permission, point the package at Laravel Gate ability names. Any roles plugin (or your own logic) can define those abilities — the package only calls Gate::allows(...).

1. Publish config (if you have not already)

2. Define Gate abilities in your app

Register them in AppServiceProvider, AuthServiceProvider, or wherever you define policies — using whatever permission system you already have.

Custom / simple:

Spatie Laravel Permission (or any package that exposes $user->can(...)):

Ability names are arbitrary — use whatever strings you prefer, then mirror them in config.

3. Point the package at those abilities

In config/filament-dbview.php:

Or via environment-driven config if you prefer:

Export: feature flag vs gate

Behaviour summary

• All authorization keys null → any user who can access the Filament panel can use DB View (subject to table scope: models vs allTables(), etc.), including CSV/JSON export when features.export is true.
• gate set → user must pass that ability or both pages are hidden / denied.
• query_runner_gate set → user must also pass it to open Query Runner; Browser still only needs gate.
• table_gate set → sidebar, browser, runner scope, and structure only include tables for which the Gate returns true.
• export_gate set → user must also pass it to download CSV/JSON (and must still be allowed to run queries). Export actions re-check the gate server-side.
• features.export => false → export is off for everyone, regardless of gates.

If you do not need role-based restrictions, leave the authorization section untouched.

Security model (read-only in depth)

Direct database access is guarded on multiple, independent layers — see ReadOnlyGuard:

1. Lexical allowlist — only a single SELECT / WITH … SELECT statement is accepted. Stacked statements, executable comments (/*! … */, /*+ … */), and many write/DDL/file/DoS tokens (INSERT, UPDATE, DROP, INTO OUTFILE, LOAD_FILE, SLEEP, lock helpers, …) are rejected. Strings and comments are stripped before keyword scanning. Schema/database-qualified names (other_db.users) are refused. Prefer a SELECT-only DB user as the strongest write barrier (see below).
2. Table scope — default models scope: only discovered models the user may see. connection scope (->allTables()): any real table on an allowed connection (optional denyTables()). The Browser is always model-only.
3. Connection allowlist — the runner may only use connections derived from discovered models (or an explicit connections.allowed list).
4. Enforced LIMIT and statement timeout cap runaway queries.
5. Rolled-back transaction (Query Runner) — reads run inside a transaction that is always rolled back (including EXPLAIN ANALYZE). The Browser uses Eloquent reads with optional read-only connection remaps and timeouts.
6. Optional dedicated read-only connection — map app connections to a DB user granted only SELECT (recommended for production).

SQL analysis limits

The Query Runner uses a lexical analyzer (SqlAnalyzer), not a full SQL engine grammar. It is built for security questions (one statement? read-only? which tables? sensitive columns?) and is intentionally fail-closed on many ambiguous forms.

What it handles well today:

• Single SELECT / WITH … SELECT (including multiple CTEs and RECURSIVE)
• Comma joins and JOINs; quoted identifiers (backticks / "…" / […])
• Rejecting stacked statements, executable comments, many write/DoS tokens
• Rejecting schema/database-qualified table names (other_db.users)
• Rejecting row-lock clauses (FOR UPDATE, FOR SHARE, SKIP LOCKED, LOCK IN SHARE MODE, …) so the viewer cannot block other sessions
• Postgres-style AS MATERIALIZED / AS NOT MATERIALIZED CTEs

Practical guidance:

• Prefer bare table names from the sidebar (logical names the app already knows).
• If a complex CTE or dialect-specific form is rejected, simplify the SQL or split the query; report persistent false denies with a minimal repro.
• The analyzer is one layer only — pair it with a SELECT-only database user for the strongest write prevention.

Additional controls:

• Sensitive-column redaction (password, *_token, *_secret, …) in the browser, the runner, and exports (including common alias/expression cases).
• Authorization — allow any panel user by default; optional Laravel Gates (see Authorization (opt-in)).
• Auditing — every allowed/denied Query Runner attempt is written to a PSR-3 log channel (see Auditing); the history table is used only when features.history is enabled.

Configuration

Everything is configured in config/filament-dbview.php. The most useful knobs:

After changing models or discovery config with the registry cache enabled, clear it (see Model discovery & registry cache):

Development

Changelog

See CHANGELOG.md for a list of changes per release.

License

MIT. See LICENSE.md.