django-haystack / django-haystack/django-haystack
denormalization and related data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 1.3k
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 3
Description
The docs confuse me about the issue of denormalization.
On the one hand, there are tools to get related data, for example, using model_attr='author__first_name', or prepare_FOO.
On the other hand, it's written that denormalization is preferred when dealing with related data under "Best practices".
Can you please elaborate on cases where denormalization is important and when it's enough to use the tools to get the related data?
I've also asked this question today in http://stackoverflow.com/questions/24136160/performance-of-denormalized-data-in-django-haystack
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Best practices documentation and the sections describing model_attr='author__first_name' and prepare_FOO. Use the linked Stack Overflow discussion as context, then clarify when denormalization is preferred versus retrieving related data. Done means the documentation explains both cases and how to choose between them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- documentation, search
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100