sridhar-s-subramanian/filament-dbview
authorization.export_gate for CSV/JSON downloads. Default null
allows any user who can run queries; set a Gate ability to restrict export by
role. Use features.export => false to disable export entirely.audit.log_sql (default true) — set false to omit full SQL from PSR-3
audit log context (metadata only: user, connection, allowed, reason, counts).->allTables(), history feature opt-in vs always-on PSR-3 audit logging, and
production guidance (dedicated log channel, filament-dbview:clear on deploy).other_db.users,
public.posts) so an allowed bare name cannot unlock another catalog.ConnectionResolver for optional read_only remaps
and applies statement timeouts on browse and relationship previews.GET_LOCK / advisory locks,
pg_terminate_backend, OPENROWSET, and related primitives.FOR UPDATE,
FOR SHARE, FOR KEY SHARE, SKIP LOCKED, NOWAIT, LOCK IN SHARE MODE).AS MATERIALIZED /
AS NOT MATERIALIZED so CTE names are not treated as real tables.features.history defaults to false so
rows are not written (and the UI panel is hidden) unless enabled — the
dbview_query_history migration still ships with the package. Enable with
DbviewPlugin::make()->history() or features.history => true. PSR-3 audit
logging is unchanged and always runs.FROM lists (FROM allowed, secret
no longer skips the second table).password AS pwd, hex(password), nested alias rewrites), not only
result column names that match redact patterns.SELECT * FROM <table>, on the table's connection) or on its structure view.?table= / ?structure= URL parameters on the Query Runner drive the prefill,
so the links are bookmarkable. Prefilled SQL still passes every read-only guard
when run, and the structure parameter stays scope-checked.SELECT, validate it through the same read-only guards, and only then
prepend a driver-aware EXPLAIN / EXPLAIN ANALYZE prefix — so the analysed
statement is always a single read-only SELECT (never EXPLAIN ANALYZE DELETE).features.structure flag.getTables() to span all schemas).SELECT console with CSV/JSON export, per-user
query history, and saved queries.LIMIT + statement timeout, always-rolled-back transactions,
an optional dedicated read-only connection, sensitive-column redaction,
optional authorization gates (allow-by-default when unset), and auditing.->allTables() / ->denyTables()),
with prefix-resilient handling of prefixed and non-prefixed tables.How can I help you explore Laravel packages today?