Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tatl GenericForeignKey should be replaced with something less bad #49

Open
SamStudio8 opened this issue Mar 5, 2021 · 0 comments
Open
Assignees
Labels
post-COG These changes will probably not be implemented in the COG-UK Majora instance

Comments

@SamStudio8
Copy link
Owner

Apparently GFK's are garbage (https://lukeplant.me.uk/blog/posts/avoid-django-genericforeignkey/) and I can see why. I suggest removing the GFK and using an Artifact, Group and possibly Process FK in its place.

@SamStudio8 SamStudio8 added the post-COG These changes will probably not be implemented in the COG-UK Majora instance label Mar 5, 2021
@SamStudio8 SamStudio8 self-assigned this Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
post-COG These changes will probably not be implemented in the COG-UK Majora instance
Projects
None yet
Development

No branches or pull requests

1 participant