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

Issue #1111: make ForeignKeys resolve symmetrically #1112

Conversation

tcleonard
Copy link
Collaborator

No description provided.

@zbyte64
Copy link
Collaborator

zbyte64 commented Feb 10, 2021

Thank you for this, was having trouble wrapping my head around this but the added tests help a bunch. I'm going to spend some time to see if we can eliminate that extra query...

@tcleonard tcleonard force-pushed the users/tcleonard/issue-#1111-fix_foreign_key_field branch from 76bac57 to e392c0f Compare January 4, 2022 10:52
@tcleonard tcleonard force-pushed the users/tcleonard/issue-#1111-fix_foreign_key_field branch from e392c0f to 9d564a0 Compare March 20, 2022 20:45
@tcleonard tcleonard force-pushed the users/tcleonard/issue-#1111-fix_foreign_key_field branch 2 times, most recently from 041299c to b8025b0 Compare September 19, 2022 13:15
@firaskafri firaskafri closed this Sep 24, 2022
@firaskafri firaskafri reopened this Sep 24, 2022
@firaskafri
Copy link
Collaborator

@tcleonard I guess this only needs formatting?

@tcleonard tcleonard force-pushed the users/tcleonard/issue-#1111-fix_foreign_key_field branch from b8025b0 to 9b2d042 Compare September 26, 2022 14:36
@firaskafri firaskafri closed this Jan 9, 2023
@tcleonard tcleonard deleted the users/tcleonard/issue-#1111-fix_foreign_key_field branch January 30, 2024 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants