PositionPaper objects with no Assignment

There is currently a one-to-one relationship between Assignment and PositionPaper objects such that when Assignments are deleted, the corresponding PositionPaper objects get deleted. In manual testing there does not seem to be an issue with this, but during live registration, the database occasionally becomes populated with PositionPaper objects with no corresponding Assignment object, causing the server to error when viewing Assignments in Admin view. Further investigation will be needed to figure out the root cause of this bug.

Seems to be SET_NULL on delete rather than CASCADE:

huxley/huxley/core/models.py

Lines 500 to 501 in fcfdf2e

    
           paper = models.OneToOneField( 
        
               PositionPaper, on_delete=models.SET_NULL, blank=True, null=True)

PositionPaper objects are left in the table with the Assignment field as NULL. Most likely this is resulting in an error when calling PositionPaper.__str__

	paper = models.OneToOneField(
	PositionPaper, on_delete=models.SET_NULL, blank=True, null=True)