Context Navigation

Changes between Initial Version and Version 1 of Ticket #32344

initial	v1
8	8	}}}
9	9
10		Currently, `postgres_options` in this case is not passed to the `SchemaEditor.create_model()` call during the migration, even if it is serializable. The usefulness of a custom `SchemaEditor` is hindered if it is unable to see this extra model configuration during migrations, as this is usually the only place that a `SchemaEditor` is invoked.
	10	Currently, `postgres_options` in this case is not passed to the `SchemaEditor.create_model()` call during the migration, even if it is serializable. The usefulness of a custom `SchemaEditor` is hindered if it is unable to see this extra model configuration during migrations, as this is usually the only place that a `SchemaEditor` is invoked. We are already unable to add any additional `Meta` options, so it seems like there is not currently a natural place for extra table level configuration that can be tracked by migrations.
11	11
12	12	This could enable user-defined `ModelState` in migrations, and allow third-party database backends to more easily participate in the migrations framework.