Otimizar carregamento de formulário de periódico com select_related e prefetch_related #1286
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
O que esse PR faz?
Elimina problema de N+1 queries no formulário de periódico do admin através de otimizações de queryset. Carregamento que gerava centenas/milhares de queries individuais agora usa poucos queries bulk otimizados.
Onde a revisão poderia começar?
journal/wagtail_hooks.py- métodoFilteredJournalQuerysetMixin.get_queryset()(linhas 134-246)Como este poderia ser testado manualmente?
/admin/snippets/journal/journal/ou/admin/snippets/journal/journalproxyeditor/Algum cenário de contexto que queira dar?
O formulário possui 50+ inline panels e relacionamentos (owner_history, publisher_history, mission, ethics, policies, etc). Sem otimizações, Django executa query separada para cada relacionamento ao renderizar o form.
Otimizações aplicadas:
Screenshots
N/A - otimização de performance backend
Quais são tickets relevantes?
Issue sobre carga lenta do formulário de journal
Referências
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.