You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The null=True constraint for the first_name field was dropped from the Student model on that commit. However, when creating migrations, Django requires a default value to be either specified on the model definition itself or specified as a one-off-value while the migrations are being run.
I've specified it as the string "one-off-value" itself for all the first_name fields that were null (so that we can query for the string and get all the records). We'll have to decide what to do with it. Most probably just replace it with empty strings since those fields were anyway Null.
The text was updated successfully, but these errors were encountered:
Yeah that is what i did when i ran it at my end too.
With SSA data coming in, I am assuming that the data will have to be cleaned and we can make sure this one of the checks.
0244358#diff-690df693064f3c683737794f9d6c9b15L104
The
null=True
constraint for thefirst_name
field was dropped from the Student model on that commit. However, when creating migrations, Django requires a default value to be either specified on the model definition itself or specified as a one-off-value while the migrations are being run.I've specified it as the string
"one-off-value"
itself for all thefirst_name
fields that were null (so that we can query for the string and get all the records). We'll have to decide what to do with it. Most probably just replace it with empty strings since those fields were anyway Null.The text was updated successfully, but these errors were encountered: