liveBook · Manning

Backup and restore

As explained in Django in Action

A database backup is a restorable copy of database contents and structure saved separately from the live database.

A database backup is a restorable copy of database contents and structure kept separately from the live database. It is the safety net for schema changes that can erase existing data. section 10.2

Django migrations track table structure, not table contents. Removing a model field removes its database column and all data in it; there is no built-in undo. Make a backup before destructive changes. section 10.2

Changing the Promoter model

Replacing first_name and last_name with full_name and common_name requires deciding how existing rows will be converted. A backup preserves those rows if the migration or its assumptions go wrong. section 10.2

How Django in Action covers it

How deep it goes
Explains the need for backups through column deletion and irreversible data loss, but does not detail backup or restore commands.
Examples
Uses the Promoter model’s name-field replacement to illustrate why existing database rows need protection.
What you can do after
Apply it by preserving a restorable database copy before removing fields or moving stored content.
How it connects
Connects database backups with Django migrations, model fields, table structures, and data transformation.

Also explained in

Compare how 10 books explain backup and restore →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Django in Action. The section links point to the parts of the book it draws on.