Context Navigation

Changes between Initial Version and Version 1 of Ticket #35383, comment 1

initial	v1
4	4
5	5	> This is particularly important in my case. I have the same Django project being deployed in different regions of the world.
6		I'd like to create the index concurrently out-of-business hours, which varies depending on the country. Following that, I'd like to create the migration file so that all environments are in sync.
	6	> I'd like to create the index concurrently out-of-business hours, which varies depending on the country. Following that, I'd like to create the migration file so that all environments are in sync.
7	7
8	8	In my opinion, your use case goes too far beyond Django to inform any changes to the framework. You can use `RunSQL` within your migration with the `IF NOT EXISTS` clause. That seems a small price to pay for enforcing your particular deployment scheme.