Class SeparateDatabaseAndState
Take two lists of operations - ones that will be used for the database,
Declaration
source linkDocumentation
and ones that will be used for the state change. This allows operations
that don't support state change to have it applied, or have operations
that affect the state or not the database, or so on.
Methods
▷ def __init__(self, database_operations=None, state_operations=None) ▶ def database_backwards(self, app_label, schema_editor, from_state, to_state) overrideinherited doc Perform the mutation on the database schema in the reverse direction - e.g. if this were CreateModel, it would in fact drop the model's table.
▶ def database_forwards(self, app_label, schema_editor, from_state, to_state) overrideinherited doc Perform the mutation on the database schema in the normal (forwards) direction.
▶ def deconstruct(self) overrideinherited doc Return a 3-tuple of class import path (or just name if it lives under django.db.migrations), positional arguments, and keyword arguments.
▶ def describe(self) overrideinherited doc Output a brief summary of what the action does.
▶ def state_forwards(self, app_label, state) overrideinherited doc Take the state from the previous migration, and mutate it so that it matches what this migration would perform.