Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

Lovable won't rename or delete a column? It's a safety setting

Ship ItChecked against the official source

Source checked 22 Oct 2026 · Published 23 Oct 2026 · Last reviewed 23 Oct 2026 · By Ctrl+Z Therapy (how we test)

The short answer

That's on purpose. In a Lovable Cloud database, Lovable refuses changes that could break your published app: dropping or renaming a table or column, changing a column's type, or adding a required column without a default value. Instead, it reaches the same result by adding to your database, for example by adding a new column and copying the data over, and the old column stays in place.

What to do

  1. Open your agent permissions (Cloud tool settings) in Lovable.
  2. Set Execute backward incompatible database migrations to Ask each time (or Always allow).
  3. With Ask each time, Lovable shows you the SQL and asks for your approval before it applies the change.

Good to know

  • Since October 7, 2026, Lovable records each database change as a migration file under drizzle/migrations/. Leave the drizzle files as they are.

Source

Checked on 22 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.