Replies: 1 comment
|
Not staff; this is what the public contract says, plus how to make the SQL safe anyway. What is documented:
Changes that remove the unknowns:
On BEGIN/COMMIT: if the service wraps the body in its own transaction, Postgres only warns on the inner |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Management API migration contract clarification
Please confirm the supported contract for
POST /v1/projects/{ref}/database/migrationsbefore a controlled migration of an existing non-production project. No request through this route has been submitted.Official references:
The unchanged, reviewed SQL query is 1,148,427 UTF-8 bytes. Compact JSON with
nameandqueryis 1,245,567 bytes. Its shape is:This is an illustrative shape, not an executable reproduction or the private migration.
Please point to authoritative implementation or contract documentation. We will not use SQL Editor/direct SQL with manual history insertion, alter SQL to evade confirmation, or retry an ambiguous submission.
This documentation request concerns an independent API route; it does not assert a root cause or fix for supabase/mcp#472. No credentials, project identifiers, business data or private SQL are included.
All reactions