Re: [Django] #18668: Make related_query_name more configurable

[Django]

#18668: Make related_query_name more configurable
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 #22207 [b77f26313cddbfde20dcf2661e9bd35458c2d1bd] fixed the remaining case
 of generic relations.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.cb499e0fee505a71c6f015a385a44bc5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18668: Make related_query_name more configurable

[Django]

#18668: Make related_query_name more configurable
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:  0 => 1


Comment:

 Part of what's included in the PR above was committed in
 99b467f272da91b8894dc90d793d8d2c40b78d8c and
 12cb0df10f12e715bcaafbee4290c92d4ed6f111. It looks like the PR contains
 some things that weren't added (e.g. adding this on generic relations) but
 it needs to be updated to merge cleanly.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.443c89ec3c2034bc0135125390610824%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18668: Make related_query_name more configurable

[Django]

#18668: Make related_query_name more configurable
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/693

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0e339219e67f6e6e3bfc87f0f632d0f0%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18668: Make related_query_name more configurable

[Django]

#18668: Make related_query_name more configurable
-+-
 Reporter:  zmsmith  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 It took me quite some time to understand the problem described here, but I
 think it's valid.

 I'll rephrase it to ensure we're talking about the same thing, and for the
 benefit of other contributors.

 The OP's description translates to the following models:

 {{{
 from django.db import models

 class Bar(models.Model):
 pass

 class Foo(models.Model):
 name = models.CharField(max_length=100)
 bar = models.ForeignKey(Bar)
 }}}

 With these definitions, you can do:

 {{{
 bar.foo_set.all()
 Bar.objects.filter(foo__name__contains='xxx')
 }}}

 Now, if you add `related_name='fizz_set'` to the `ForeignKey` declaration,
 you can do:

 {{{
 bar.fizz_set.all()
 Bar.objects.filter(fizz_set__name__contains='xxx')
 #  -- ugly!
 }}}

 And if you add `related_name='fizz'` it doesn't improve the situation:
 {{{
 bar.fizz.all()
 #   -- ugly!
 Bar.objects.filter(fizz__name__contains='xxx')
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.