Repository navigation
supabase-dashboard 0.1.0-dev.4
Pre-releaseWhat's new
Tables in the Table editor now open on a Data tab that shows their rows, 50 per page, with Previous and Next. The column list from 0.1.0-dev.3 moved to a Definition tab. Every member can read rows, viewers included. Nothing can be edited yet.
The dashboard reads rows through the stack's postgres-meta (/pg/query behind the gateway) with the service role key saved on the Settings tab. The key stays on the server. The server writes the query itself: one SELECT in a read-only transaction with a 5 second statement timeout. Table and column names come from postgres-meta and are always quoted, and nothing typed in the browser goes into the SQL.
Pages are sorted by primary key. A table without one is read in no fixed order, and the page warns that pages can overlap while the table changes. If the database hits the 5 second limit, the page says so instead of showing a generic error.
Upgrading from 0.1.0-dev.3
Pull the new image. There are no new migrations or configuration settings.
Known limitations
- Rows are read with postgres-meta's database role, which in a standard stack bypasses row-level security. Anyone who can open the project sees every row.
- Each value is cut to 200 characters, and only the first 50 columns are shown. The Definition tab still lists all of them.
- Paging stops at page 2000 (100,000 rows). Later pages of a large table get slower, since PostgreSQL reads every earlier row first.
- No filters, sorting, or row editing. Views, foreign tables, and foreign key details aren't shown.
- Earlier limits still apply: up to 1000 tables per schema and 500 schemas, schemas with a comma in the name can't be opened, and only the Kong gateway is tested.
Install
Container image (linux/amd64, linux/arm64):
docker pull ghcr.io/filipnone/supabase-dashboard:0.1.0-dev.4
To deploy on a Linux server with Docker, download supabase-dashboard-0.1.0-dev.4-docker.tar.gz, unpack it, and follow its README. Nothing is compiled on the server.
The *-linux-gnu.tar.gz files contain the same server binary and web assets for running without Docker (glibc 2.36 or newer).
This is a development pre-release. Expect breaking changes between dev releases. Database migrations only move forward: back up the metadata database before upgrading, and do not downgrade.