Database Projects for Read-Only Structure and Migration Checks

Use the Supabase guide for scoped, read-only schema inspection, migration-history comparison, and approved queries. One project is currently listed.

Inspect Structure and Migration Records with Read-Only Evidence

The current collection centers on read-only Supabase inspection through MCP. Start with a local or approved development project, confirm the project reference, and enable only the necessary tool groups. Compare table metadata and migration history before considering changes. Any approved query should return only the fields or aggregates required for the question; read-only access can still expose sensitive data. Writes and migration execution are outside the listed Supabase guide’s task scope.

Databases Projects

Supabase
Build applications on a Postgres-backed platform with authentication, storage, APIs, functions, and realtime capabilities, using hosted or self-hosted deployment workflows.
Supabase
- Development Workflows
- Databases
- Databases
- Postgres
- Supabase

Skills supply instructions; projects supply software or supporting resources. Check each source for setup, runtime, access, and license requirements.

Choose by the Job

Inventory table structure

Compare table metadata with the application code without exporting row data.

Compare migration history

Match recorded migrations with repository files and report missing or extra records before any execution.

Check a bounded query

Review a permitted SELECT and return the minimum aggregate or sanitized output needed to answer the question.

Explore Related Task Categories

Find instructions and software for the next stage of your work, from code changes and interface design to office tasks and media production.

Frequently Asked Questions

Should I inspect schema or query rows first?

Start with table metadata when the question concerns columns, types, or relationships. Request an approved, bounded query only when metadata cannot answer the question.

What can migration history comparison establish?

It can identify missing or extra migration records relative to repository files. It does not prove that every live table matches the intended schema; compare table metadata separately.

Does this guide authorize migration execution?

No. Its task is read-only inspection and migration-history comparison. Treat writes as a separate task with explicit authorization and independent verification.

What belongs in a database task request?

Include schema, intended outcome, sample inputs, role, and verification criteria. Omit credentials and sensitive rows.

Can read-only inspection validate every access policy?

No. Schema and approved queries provide limited evidence. Testing every allowed and denied action requires a separate role-based test plan.

Is production data needed for diagnosis?

Prefer a representative sanitized dataset. If production access is necessary, agree on the minimum permitted operations first.

Inspect a Scoped Database Project

Bring schema metadata and migration files; keep credentials out of the conversation and request a read-only comparison.

Download Floatboat