#34122: models.ForeignObject is missing documentation
-------------------------------------+-------------------------------------
               Reporter:  Ömer       |          Owner:  nobody
  Faruk Abacı                        |
                   Type:             |         Status:  new
  Cleanup/optimization               |
              Component:             |        Version:  4.1
  Documentation                      |       Keywords:  custom join,
               Severity:  Normal     |  multiple column join, foreignobject
           Triage Stage:             |      Has patch:  0
  Unreviewed                         |
    Needs documentation:  0          |    Needs tests:  0
Patch needs improvement:  0          |  Easy pickings:  0
                  UI/UX:  0          |
-------------------------------------+-------------------------------------
 While trying to implement a custom multiple-column join I have spent hours
 to find an elegant way, at the end I have found an old issue here:

 https://code.djangoproject.com/ticket/19385

 Then I have realized that I can use `ForeignObject` for custom joins.
 Almost all of the solutions online suggest using raw SQLs with
 `Manager.raw()` or `QuerySet.extra()`, none of them mention about
 `ForeignObject`. I don't know if it was on purpose or not but I thought
 that it might be good to mention about the `ForeignObject` in the
 following section:

 https://docs.djangoproject.com/en/4.1/ref/models/relations/

 What do you think?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34122>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184150b849c-b0756dac-303c-4b65-90e5-3c4d2d2256d4-000000%40eu-central-1.amazonses.com.

Reply via email to