Skip to content

fix(converter.py): performance fix in `convert_field_to_djangomodel.dynamic_type.CustomField#1391

Closed
mahdyhamad wants to merge 5 commits into
graphql-python:mainfrom
mahdyhamad:fix_custom_resolver_multi_db_hits
Closed

fix(converter.py): performance fix in `convert_field_to_djangomodel.dynamic_type.CustomField#1391
mahdyhamad wants to merge 5 commits into
graphql-python:mainfrom
mahdyhamad:fix_custom_resolver_multi_db_hits

Conversation

@mahdyhamad

Copy link
Copy Markdown
Collaborator

Fix performance issue in resolving one-to-one and foreign-key field, make only one database hit to get the field instance while resolving the field.

@mahdyhamad

Copy link
Copy Markdown
Collaborator Author

Related issues:

PR caused the issue: #1315

…ynamic_type.CustomField`. Get instance from the database only one time.
@mahdyhamad mahdyhamad force-pushed the fix_custom_resolver_multi_db_hits branch from 1a3c76c to 7fa8d1f Compare March 8, 2023 15:43
@mahdyhamad mahdyhamad marked this pull request as draft March 8, 2023 15:43
@grantmcconnaughey

Copy link
Copy Markdown

This seems to be related to #1375

@mahdyhamad mahdyhamad marked this pull request as ready for review March 19, 2023 14:51
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