Skip to content
This repository was archived by the owner on Apr 21, 2023. It is now read-only.
This repository was archived by the owner on Apr 21, 2023. It is now read-only.

Deleting sets, chapters or levels manually via Django Admin can cause problems with the ExtendedUser #5

@ampled

Description

@ampled

I'm pretty sure this problem happens because the extendeduser uses OneToOneFields to relate a user to a Set/Chapter/Level. This could probably easily be fixed by reworking the "Current X"-fields in ExtendedUser to ForeignKey instead. However, this could cause problems with existing data in the database.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions