Trying to run update_or_create on CourtRegistry (for KL) with the court being nullable causes a bunch of errors.
This field should be non nullable anyway. since it derives the code from the court if it doesn't have its own.
Django complained that you cannot change a nullable field to non nullable without a default. The field was set as required in the admin so all existing registries across all LIIs should already have a court so I don't think we need to have a default.
Trying to run update_or_create on CourtRegistry (for KL) with the court being nullable causes a bunch of errors. This field should be non nullable anyway. since it derives the code from the court if it doesn't have its own. Django complained that you cannot change a nullable field to non nullable without a default. The field was set as required in the admin so all existing registries across all LIIs should already have a court so I don't think we need to have a default.