zulip/confirmation/migrations
Mateusz Mandera 676edb3802 confirmation: Migration to add expiry_date step 1.
The commit:
1. Adds the new field as nullable.
2. Adds code that'll create new Confirmation with the field set
   correctly.
3. For verifying validity of Confirmation object this still uses the old
   logic in get_object_from_key() to keep things functioning until we
   backfill the old objects in the next step.

Thus this commit is deployable. Next we'll have a commit to run a
backfill migration.
2021-09-06 17:28:29 -07:00
..
0001_initial.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0002_realmcreationkey.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0003_emailchangeconfirmation.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0004_remove_confirmationmanager.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0005_confirmation_realm.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0006_realmcreationkey_presume_email_valid.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0007_add_indexes.py python: Normalize quotes with Black. 2021-02-12 13:11:19 -08:00
0008_confirmation_expiry_date.py confirmation: Migration to add expiry_date step 1. 2021-09-06 17:28:29 -07:00
__init__.py Include autogenerated initial migrations for South. 2013-01-08 18:14:39 -05:00