Re: [Django] #25280: django 1.9 using validators.validate_slug will recreate migrations over and over

[Django]

#25280: django 1.9 using validators.validate_slug will recreate migrations over 
and
over
-+-
 Reporter:  chenull  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  migrations,  | Triage Stage:
  validators, slug   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chenull):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


--
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.6323476e7b6d3b6e388e5dfef270b352%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25260: Sets in "in" lookups should be converted to list if backend doesn't support sets

[Django]

#25260: Sets in "in" lookups should be converted to list if backend doesn't 
support
sets
-+-
 Reporter:  Naddiseo |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * resolution:  worksforme => invalid


--
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/066.72b0a0778a605f08d4f8fa94c0cce040%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

[Django]

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  multiple-| Triage Stage:  Accepted
  inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I guess this issue has since been fixed (unless the regression tests in
 the second pull request don't capture the issue). Please open a new ticket
 if issues remain, thanks!

--
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/064.d94511365fbe4ae45d31471567c202db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21554: incorrect SQL generated when using multiple inheritance

[Django]

#21554: incorrect SQL generated when using multiple inheritance
-+-
 Reporter:  pegler   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multiple-| Triage Stage:  Accepted
  inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"7eb513ab0f761fe88aa4d3579fdf8706741f2239" 7eb513ab]:
 {{{
 #!CommitTicketReference repository=""
 revision="7eb513ab0f761fe88aa4d3579fdf8706741f2239"
 Refs #21554 -- Added some assertions to a model_inheritance_regress test.
 }}}

--
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/064.18ae0fa924141884e00506c95efba24a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19263: Filtering __in a sliced queryset with a 0 limit raises an error (was: DatabaseError on using empty Page .object_list in __in clause in a query)

[Django]

#19263: Filtering __in a sliced queryset with a 0 limit raises an error
-+-
 Reporter:  chkwok@… |Owner:  biern
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/5139 PR]

--
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/077.17a9175a67be347b03a20eb66adef345%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24196: Filtering __in a sliced queryset with a 0 limit raises an unexpected error

[Django]

#24196: Filtering __in a sliced queryset with a 0 limit raises an unexpected 
error
-+-
 Reporter:  BertrandBordage  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.7
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Duplicate of #19263

--
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/073.e4b27bcc86fa24c06fbc33c7e9fca171%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15049: Using annotation before and after filter gives wrong results

[Django]

#15049: Using annotation before and after filter gives wrong results
-+-
 Reporter:  Alex |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "15049-test.diff" added.


--
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/062.8e5323a3fa60f17544c60097886ae6ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15049: Using annotation before and after filter gives wrong results

[Django]

#15049: Using annotation before and after filter gives wrong results
-+-
 Reporter:  Alex |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Confirmed it's still an issue as of
 dad8434d6ff5da10959672726dc9b397296d380b. Attaching a rebased test.

 In the interim, documentation patches would of course be welcomed.

--
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/062.404466e17d92b32c199d1f1f7f91acb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22973: cannot get SQL code of empty queryset

[Django]

#22973: cannot get SQL code of empty queryset
-+-
 Reporter:  emanuele.paolini@…   |Owner:
 |  andersonresende
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  assigned => closed
 * resolution:   => wontfix


Comment:

 My understanding is that `EmptyResultSet` is raised when valid SQL cannot
 be generated (see #19263 for an example). Therefore I'm going to mark this
 as "won't fix".

--
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/084.e214bcd89a5a5fc19794920ee3f50e16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17276: Slow anti-join query against Postgres

[Django]

#17276: Slow anti-join query against Postgres
-+-
 Reporter:  dmitry@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  orm, postgres,   | Triage Stage:  Accepted
  join, anti-join|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Fixed in Django 1.6 by 69597e5bcc89aadafd1b76abf7efab30ee0b8b1a.

--
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/075.8d0c3bd419f4ec7379badc69bba31979%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16955: Querying on the reverse of a FK with the wrong class silently returns bad data

[Django]

#16955: Querying on the reverse of a FK with the wrong class silently returns 
bad
data
-+-
 Reporter:  jdunck   |Owner:  dgouldin
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Yes, duplicate of #14334.

--
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/064.8274d759c6292d153c07a3291eb882f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25280: django 1.9 using validators.validate_slug will recreate migrations over and over

[Django]

#25280: django 1.9 using validators.validate_slug will recreate migrations over 
and
over
---+--
 Reporter:  chenull|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Migrations |Version:  master
 Severity:  Normal |   Keywords:  migrations, validators, slug
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 Using django.core.validators.validate_slug in a model will make the
 migration files on that model increment infinitely, allthough no changes
 has made in the model.
 {{{
 from django.core.validators import validate_slug

 class Organization(models.Model):
 slug = models.SlugField(unique=True, validators=[validate_slug])
 }}}

 `manage.py makemigrations`
 {{{
 Migrations for 'organizations':
   0009_auto_20150815_2151.py:
 - Alter field slug on organization
 Migrations for 'organizations':
   0010_auto_20150815_2151.py:
 - Alter field slug on organization
 Migrations for 'organizations':
   0011_auto_20150815_2158.py:
 - Alter field slug on organization
 Migrations for 'organizations':
   0012_auto_20150815_2158.py:
 - Alter field slug on organization
 }}}

 A quick fix is to workaround this issue is just copy paste the code in
 django.core.validators:
 {{{
 from django.core.validators import RegexValidator

 orgslug_validator = [
 RegexValidator(regex=r'^[-a-zA-Z0-9_]+\Z',
message=_("Enter a valid 'slug' consisting of letters,
 "
  "numbers, underscores or hyphens."),
code='invalid_slug')
 ]

 class Organization(models.Model):
 slug = models.SlugField(unique=True, validators=orgslug_validator)
 }}}

--
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/050.c718921daf47b57780cd4362a7bbd0df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25180: ArrayFields should not have varchar_patterns_ops or text_patterns_ops indexes

[Django]

#25180: ArrayFields should not have varchar_patterns_ops or text_patterns_ops
indexes
-+-
 Reporter:  fabianbuechler   |Owner:
 |  caioariede
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"29fa1b5800f2b86b9860dac38377e95f7c36063f" 29fa1b58]:
 {{{
 #!CommitTicketReference repository=""
 revision="29fa1b5800f2b86b9860dac38377e95f7c36063f"
 [1.8.x] Fixed #25180 -- Prevented varchar_patterns_ops and
 text_patterns_ops indexes for ArrayField.

 Backport of dad8434d6ff5da10959672726dc9b397296d380b from master
 }}}

--
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/072.495eeb4fe095224c2e001cb0bea728b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25180: ArrayFields should not have varchar_patterns_ops or text_patterns_ops indexes

[Django]

#25180: ArrayFields should not have varchar_patterns_ops or text_patterns_ops
indexes
-+-
 Reporter:  fabianbuechler   |Owner:
 |  caioariede
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"dad8434d6ff5da10959672726dc9b397296d380b" dad8434]:
 {{{
 #!CommitTicketReference repository=""
 revision="dad8434d6ff5da10959672726dc9b397296d380b"
 Fixed #25180 -- Prevented varchar_patterns_ops and text_patterns_ops
 indexes for ArrayField.
 }}}

--
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/072.59564d4b0e39b28e2af74dbff8d3ab66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24935: refactor conditional GET handling

[Django]

#24935: refactor conditional GET handling
--+
 Reporter:  syphar|Owner:  syphar
 Type:  Cleanup/optimization  |   Status:  closed
Component:  HTTP handling |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"7a40fef17ab7918cbb1ddc3ba080f42b420f7a48" 7a40fef]:
 {{{
 #!CommitTicketReference repository=""
 revision="7a40fef17ab7918cbb1ddc3ba080f42b420f7a48"
 Fixed #24935 -- Refactored common conditional GET handling.
 }}}

--
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/064.9b2db22f504fc69fe6f928bfa0af5a3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16603: Unnecessary join when using a reverse foreign-key filter and reverse foreign-key aggregate call

[Django]

#16603: Unnecessary join when using a reverse foreign-key filter and reverse
foreign-key aggregate call
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * Attachment "16603-test.diff" added.


--
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/068.ab9489f3e2f19019691dbf1396c8e9c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16603: Unnecessary join when using a reverse foreign-key filter and reverse foreign-key aggregate call

[Django]

#16603: Unnecessary join when using a reverse foreign-key filter and reverse
foreign-key aggregate call
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Updated test to apply cleanly and verified it's still an issue as of
 98bcdfa8bd902addd4b8cf37d039b3597d58a45c.

--
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/068.add1c2e2846f888b3bbc8ac8253e6f54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25279: Make prefetch_related_objects a public API

[Django]

#25279: Make prefetch_related_objects a public API
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by adamchainz):

 * has_patch:  0 => 1


Comment:

 Oh #24975 is nice. It doesn't seem that hard to do - on Model would it not
 just require...

 {{{
 def prefetch_related(self, related_lookups):
 prefetch_related_objects([self], related_lookups)
 }}}

 Basic PR at [https://github.com/django/django/pull/5138], with a
 documentation sketch. Agree that more tests would be required.

--
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/068.2e40f2c4f679409898ace606d0bd1d18%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24975: Add the ability to prefetch_related() from a model instance (was: Prefetch_related from object directly)

[Django]

#24975: Add the ability to prefetch_related() from a model instance
-+-
 Reporter:  duduklein|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

--
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/067.9b0a7b55bd2293f746bd023fecf7a79f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25279: Make prefetch_related_objects a public API

[Django]

#25279: Make prefetch_related_objects a public API
-+-
 Reporter:  adamchainz   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Seems related to #24975 which proposes to add the ability to call
 `prefetch_related()` on a model instance. I wonder if we could find a
 common solution to address both of these tickets.

 If we make `prefetch_related_objects()` public, I think some tests would
 also be needed to ensure that it isn't refactored so that it's signature
 changes.

--
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/068.aac31ea0c930c5f088ff77a18e00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

[Django]

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  megaumi
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  F(), ORM, distinct   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1f7b25c1a7a85426675a04380f37b180edc08bbc" 1f7b25c]:
 {{{
 #!CommitTicketReference repository=""
 revision="1f7b25c1a7a85426675a04380f37b180edc08bbc"
 Fixed #24986 -- Added support for annotations in DISTINCT queries.
 }}}

--
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/062.93e8297f4453ac6a6e3a0bf1d460abad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #25279: Make prefetch_related_objects a public API

[Django]

#25279: Make prefetch_related_objects a public API
--+
 Reporter:  adamchainz|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 `prefetch_related` is great, but it would be nice to be able to reuse its
 capabilities with lists of model instances already retrieved by other code
 (or from cache, or newly constructed, etc.). It seems this is possible by
 using `django.db.models.query.prefetch_related_objects` which is the
 function implementing all the prefetch capability - I've just seen it used
 fine, however it is not part of Django's public API.

 As far as I can tell, just doing an `import` in
 `django.db.models.__init__` and adding documentation should be enough to
 make it public, since `prefetch_related_objects` contains all the
 functionality that `prefetch_related` exposes.

--
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/053.824e349b0c8eec33a2fba6fd81d3cacc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15020: Redundant joins generated when using reverse foreign key

[Django]

#15020: Redundant joins generated when using reverse foreign key
-+-
 Reporter:  adurdin  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Seems to be fixed in Django 1.6.

--
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.56f7ce0c923d63a2b43ac4141bea9adf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24986: Selecting distinct on lower() function throws AttributeError("'Func' object has no attribute 'column'")

[Django]

#24986: Selecting distinct on lower() function throws AttributeError("'Func' 
object
has no attribute 'column'")
-+-
 Reporter:  wbar |Owner:  megaumi
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  F(), ORM, distinct   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


--
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/062.b9b51848196c94180188f12c6986a249%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25064: Join.as_sql() emits invalid SQL if get_joining_columns() returns an empty tuple

[Django]

#25064: Join.as_sql() emits invalid SQL if get_joining_columns() returns an 
empty
tuple
-+-
 Reporter:  AlexHill |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"98bcdfa8bd902addd4b8cf37d039b3597d58a45c" 98bcdfa8]:
 {{{
 #!CommitTicketReference repository=""
 revision="98bcdfa8bd902addd4b8cf37d039b3597d58a45c"
 Fixed #25064 -- Allowed empty join columns.
 }}}

--
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/066.7db50c3d86922a0e0db4153074d1b6d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25278: call_command should allow the first param to be a module

[Django]

#25278: call_command should allow the first param to be a module
-+-
 Reporter:  mlissner |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * easy:  1 => 0
 * needs_docs:   => 0
 * resolution:   => wontfix


Comment:

 I don't think the IDE renaming advantages provide sufficient justification
 for the additional complexity that would be required, but feel free to
 raise the idea on the DevelopersMailingList to get more feedback. The
 reason `ForeignKey` also accepts a string is to avoid circular references.

--
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/066.5e9cd247c118c1a7dd4d968a1dbc3158%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12856: Decide on public API/documentation for form.BoundField attributes

[Django]

#12856: Decide on public API/documentation for form.BoundField attributes
-+-
 Reporter:  mnbayazit|Owner:  MoritzS
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  boundfield required  | Triage Stage:  Accepted
  is_hidden auto_id  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by MoritzS):

 * needs_better_patch:  1 => 0


Comment:

 Updated PR

--
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/067.f772c261e28c6c9a38a13fe9f2be0c93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.