db.migrations.operations.SeparateDatabaseAndState

class SeparateDatabaseAndState(database_operations=None, state_operations=None) [source]

A highly specialized operation that let you mix and match the database (schema-changing) and state (autodetector-powering) aspects of operations.

It accepts two list of operations, and when asked to apply state will use the state list, and when asked to apply changes to the database will use the database list. Do not use this operation unless you’re very sure you know what you’re doing.

Links:

https://docs.djangoproject.com/en/1.10/ref/migration-operations/#django.db.migrations.operations.SeparateDatabaseAndState

doc_Django

2016-10-09 18:35:11

Comments

Popular Articles

db.migrations.operations.RunPython class RunPython(code, reverse_code=None, atomic=None, hints=None, elidable=False) [source] Runs custom Python code in a historical context. code (

db.migrations.operations.AlterOrderWithRespectTo class AlterOrderWithRespectTo(name, order_with_respect_to) [source] Makes or deletes the _order column needed for the order_with_respect_to option

db.migrations.operations.CreateModel class CreateModel(name, fields, options=None, bases=None, managers=None) [source] Creates a new model in the project history and a corresponding t

db.migrations.operations.AddField class AddField(model_name, name, field, preserve_default=True) [source] Adds a field to a model. model_name is the model’s name, name is the field

db.migrations.operations.RemoveField class RemoveField(model_name, name) [source] Removes a field from a model. Bear in mind that when reversed, this is actually adding a field to a m