By default, Bytebase wraps SQL statements in a transaction for safety - if something goes wrong, changes can be rolled back.Some DDL statements can’t run inside transactions. To disable transaction wrapping, add this comment before your SQL:
Copy
Ask AI
-- txn-mode=offALTER TABLE t ALTER COLUMN a TYPE VARCHAR(255);
Perfect for multi-tenant PostgreSQL setups where each database has its own owner.When enabled, Bytebase automatically switches to the database’s OWNER role before executing changes, ensuring proper permissions.Location: Project → Settings → Issue Related
By default, issue creators can’t approve their own changes.To allow self-approval, enable Allow self approval in your project settings.Location: Project → Settings → Issue Related