Re: [Django] #13312: Add a way to customize the order_by() of null fields

[Django]

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  Sergey Dobrov|Owner:  felixxm
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ordering, order_by,  | Triage Stage:  Ready for
  null   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Josh Smeaton):

 I don't like the idea of three-value logic here, because it imposes a
 slight burden when reading. It just seems unnecessary when there's nothing
 wrong with two kwarg options.

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

Re: [Django] #13312: Add a way to customize the order_by() of null fields

[Django]

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  Sergey Dobrov|Owner:  felixxm
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ordering, order_by,  | Triage Stage:  Ready for
  null   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Cloudream):

 What about one parameter with three possible values?

 nulls_first:

  - True: nulls at first
  - False: nulls at last
  - None (default): database default ordering

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

Re: [Django] #8408: Add a new meta option: don't do count(*) in admin

[Django]

#8408: Add a new meta option: don't do count(*) in admin
---+---
 Reporter:  LI Daobing |Owner:  Thomas Chaumeny
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---

Comment (by Josh Smeaton):

 I don't think this ticket has been properly or fully fixed. The patch that
 landed only affects the display of filtered results. A count(*) is still
 executed every time you hit a page, which leads to timeouts when tables
 grow large.

 I think the idea of using a custom paginator is probably a good one, but
 that could probably be controlled by an option in model admin or
 something. I'm not reopening this ticket until I've got some feedback
 first.

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

Re: [Django] #27582: PostgreSQL form and model HStoreFields do not support writing null values

[Django]

#27582: PostgreSQL form and model HStoreFields do not support writing null 
values
+--
 Reporter:  David Hoffman   |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  contrib.postgres|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  hstore hstorefield  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by David Hoffman):

 I have opened a pull request at https://github.com/django/django/pull/7668

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

Re: [Django] #27582: PostgreSQL form and model HStoreFields do not support writing null values (was: PostgreSQL form and model HStoreFields do not support null values)

[Django]

#27582: PostgreSQL form and model HStoreFields do not support writing null 
values
+--
 Reporter:  David Hoffman   |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  contrib.postgres|  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  hstore hstorefield  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by David Hoffman):

 * status:  assigned => new


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

[Django] #27582: PostgreSQL form and model HStoreFields do not support null values

[Django]

#27582: PostgreSQL form and model HStoreFields do not support null values
-+-
   Reporter:  David  |  Owner:  (none)
  Hoffman|
   Type:  Bug| Status:  assigned
  Component: |Version:  master
  contrib.postgres   |
   Severity:  Normal |   Keywords:  hstore hstorefield
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 = Overview

 PostgreSQL allows values to be either strings or nulls in `hstore`:
 https://www.postgresql.org/docs/9.5/static/hstore.html

 It appears that the form and model HStoreFields do not support null
 values. Is this something that should be fixed?

 = How to reproduce for the form field

 {{{
 >>> from django.contrib.postgres import forms
 >>> field = forms.HStoreField()
 >>> field.clean('{"a": null}')
 {u'a': u'None'}
 }}}
 == Expected Behavior

 The null has been converted to a string, when it should actually be the
 None value

 = How to reproduce for the model field

 {{{
 >>> from django.contrib.postgres.fields import HStoreField
 >>> field = HStoreField()
 >>> field.clean({'a': None}, None)
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/dhoffman/.envs/brain-campaign/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py", line 588, in clean
 self.validate(value, model_instance)
   File "/Users/dhoffman/.envs/brain-campaign/lib/python2.7/site-
 packages/django/contrib/postgres/fields/hstore.py", line 36, in validate
 params={'key': key},
 ValidationError: [u'The value of "a" is not a string.']
 }}}

 == Expected Behavior

 This should actually be allowed without error.

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

Re: [Django] #27310: Refactor RenameModel.state_forwards to avoid relying on state.apps.

[Django]

#27310: Refactor RenameModel.state_forwards to avoid relying on state.apps.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 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):

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

Re: [Django] #27572: Static files served in development should prevent caching

[Django]

#27572: Static files served in development should prevent caching
-+-
 Reporter:  Kevin Christopher|Owner:  nobody
  Henry  |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.staticfiles  |  Version:  1.10
 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
-+-

Comment (by Tim Graham):

 We've [https://groups.google.com/d/topic/django-
 developers/N0KbgDeLuUE/discussion been thinking about] replacing our own
 staticfile serving code with something like
 [https://github.com/evansd/whitenoise whitenoise]. Do you know if it has a
 suitable option?

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

Re: [Django] #27581: Second-level proxy fails to inherit reverse relation from parent proxy

[Django]

#27581: Second-level proxy fails to inherit reverse relation from parent proxy
-+-
 Reporter:  Shai Berger  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Simon Charette):

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


Comment:

 I confirmed this was fixed in Django 1.10.

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

Re: [Django] #27466: Use a datepicker widget for Date[Time]RangeField in admin

[Django]

#27466: Use a datepicker widget for Date[Time]RangeField in admin
-+-
 Reporter:  Adrien Brunet|Owner:  prabod
 |  manuranga rathnayaka
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  forms, admin,| Triage Stage:  Accepted
  jquery, datepicker |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by prabod manuranga rathnayaka):

 * owner:  nobody => prabod manuranga rathnayaka
 * status:  new => assigned


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

Re: [Django] #27355: Add PostgreSQL Extension operation example to reference page

[Django]

#27355: Add PostgreSQL Extension operation example to reference page
-+-
 Reporter:  Maxime Lorant|Owner:  ntuckovic
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres unaccent| Triage Stage:  Accepted
  trigram|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"1b6649c6d177286852cc9c13fdf0fa65f17cb1f8" 1b6649c6]:
 {{{
 #!CommitTicketReference repository=""
 revision="1b6649c6d177286852cc9c13fdf0fa65f17cb1f8"
 [1.10.x] Fixed #27355 -- Added “Creating extension using migrations” docs.

 Backport of 4de8aaf7ffc91b91cbb70e9db406abe9b160575a 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/065.1f89a8205b725071d76a81eb602cb4dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27355: Add PostgreSQL Extension operation example to reference page

[Django]

#27355: Add PostgreSQL Extension operation example to reference page
-+-
 Reporter:  Maxime Lorant|Owner:  ntuckovic
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres unaccent| Triage Stage:  Accepted
  trigram|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"4de8aaf7ffc91b91cbb70e9db406abe9b160575a" 4de8aaf]:
 {{{
 #!CommitTicketReference repository=""
 revision="4de8aaf7ffc91b91cbb70e9db406abe9b160575a"
 Fixed #27355 -- Added “Creating extension using migrations” docs.
 }}}

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

Re: [Django] #27472: GEOSGeometry('POINT EMPTY').ogr crashes

[Django]

#27472: GEOSGeometry('POINT EMPTY').ogr crashes
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  closed
Component:  GIS  |  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:"9b79281e315268bdbba2704b253eef23b46da023" 9b79281]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b79281e315268bdbba2704b253eef23b46da023"
 Fixed #27472 -- Fixed GEOSGeometry('POINT EMPTY').transform crash.
 }}}

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

Re: [Django] #27472: GEOSGeometry('POINT EMPTY').ogr crashes

[Django]

#27472: GEOSGeometry('POINT EMPTY').ogr crashes
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 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:"65a1f32319a0a58f8458060a61c7bab0fa12292e" 65a1f323]:
 {{{
 #!CommitTicketReference repository=""
 revision="65a1f32319a0a58f8458060a61c7bab0fa12292e"
 Refs #27472 -- Fixed GEOSGeometry('POINT EMPTY').ogr crash.
 }}}

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

Re: [Django] #27472: GEOSGeometry('POINT EMPTY').ogr crashes

[Django]

#27472: GEOSGeometry('POINT EMPTY').ogr crashes
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 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:"a413ef2155c4f3e5bf6954608d65a96631feb7e6" a413ef21]:
 {{{
 #!CommitTicketReference repository=""
 revision="a413ef2155c4f3e5bf6954608d65a96631feb7e6"
 Refs #27472 -- Fixed OGRGeometry('POINT EMPTY').geos crash.
 }}}

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

Re: [Django] #27566: Clarify documentation of ModelAdmin.save_model and delete_model

[Django]

#27566: Clarify documentation of ModelAdmin.save_model and delete_model
--+
 Reporter:  Doug Harris   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
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:"d978b36414da3263ac07cd5a46c6ccf46a00a5fb" d978b364]:
 {{{
 #!CommitTicketReference repository=""
 revision="d978b36414da3263ac07cd5a46c6ccf46a00a5fb"
 [1.10.x] Fixed #27566 -- Clarified overriding
 ModelAdmin.save_model()/delete_model() docs.

 Backport of 413216fb9fb36c064494fe155effc39e2888161e 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/065.73908cacc2bc78890df2714efb67940b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13312: Add a way to customize the order_by() of null fields

[Django]

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  Sergey Dobrov|Owner:  felixxm
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ordering, order_by,  | Triage Stage:  Ready for
  null   |  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:"47ef8f31f30a2b1920f82494d729c285565867dd" 47ef8f3]:
 {{{
 #!CommitTicketReference repository=""
 revision="47ef8f31f30a2b1920f82494d729c285565867dd"
 Fixed #13312 -- Allowed specifying the order of null fields in queries.

 Thanks Mariusz Felisiak for finishing the patch.
 }}}

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

Re: [Django] #27581: Second-level proxy fails to inherit reverse relation from parent proxy

[Django]

#27581: Second-level proxy fails to inherit reverse relation from parent proxy
-+-
 Reporter:  Shai Berger  |Owner:  nobody
 Type:  Bug  |   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
-+-

Comment (by Simon Charette):

 This should be fixed by 5b980897f2da3c048d88029af554e0fc4be68a8e in 1.10
 and 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/063.06c5e6ad51653aac7c836bf5fbe9585a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

[Django]

#27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000
-+-
 Reporter:  Ed Morley|Owner:
 |  Kamalavelan
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver, bind, | Triage Stage:
  loopback   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kamalavelan):

 * version:  1.10 => master


Comment:

 PR - https://github.com/django/django/pull/7666

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

Re: [Django] #27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

[Django]

#27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000
-+-
 Reporter:  Ed Morley|Owner:
 |  Kamalavelan
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver, bind, | Triage Stage:
  loopback   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kamalavelan):

 * Attachment "27537.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/066.07d783bbe764e5ac7eda7fd0830f484d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27566: Clarify documentation of ModelAdmin.save_model and delete_model

[Django]

#27566: Clarify documentation of ModelAdmin.save_model and delete_model
--+
 Reporter:  Doug Harris   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"413216fb9fb36c064494fe155effc39e2888161e" 413216fb]:
 {{{
 #!CommitTicketReference repository=""
 revision="413216fb9fb36c064494fe155effc39e2888161e"
 Fixed #27566 -- Clarified overriding
 ModelAdmin.save_model()/delete_model() docs.
 }}}

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

[Django] #27581: Second-level proxy fails to inherit reverse relation from parent proxy

[Django]

#27581: Second-level proxy fails to inherit reverse relation from parent proxy
-+-
   Reporter:  Shai   |  Owner:  nobody
  Berger |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.8
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Double proxy models are, as has been noted before, a questionable design
 decision, but they should still work (the reason here: we need more than
 one Admin interface for the parent proxy class). We have, basically, this:
 {{{
 class A(models.Model):
 pass

 class B(A):
 class Meta:
 proxy=True

 class F(models.Model):
 b = models.ForeignKey(B, related_name="bffs")

 class C(B):
 class Meta:
 proxy=True
 }}}

 and when we try
 {{{
 qset = C.objects.filter(bffs__in=whatever)
 }}}
 we get "bffs not recognized, options are ..."

 Not sure if this still happens with master, will try to repro later.

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

Re: [Django] #27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

[Django]

#27537: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000
-+-
 Reporter:  Ed Morley|Owner:
 |  Kamalavelan
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.10
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  runserver, bind, | Triage Stage:
  loopback   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Kamalavelan):

 * status:  new => assigned
 * owner:  nobody => Kamalavelan


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

Re: [Django] #27580: add special field for storing content types

[Django]

#27580: add special field for storing content types
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  New feature  |   Status:  assigned
Component:   |  Version:  master
  contrib.contenttypes   |
 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
-+-

Comment (by Jani Tiainen):

 Does this feature require changes in Django core which prevents
 implementing this as an external app? I only saw quite small change in
 actual Django core.

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

Re: [Django] #13089: Support Negative Indexing on QuerySets

[Django]

#13089: Support Negative Indexing on QuerySets
-+-
 Reporter:  Adam Nelson  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  feature  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Florian Verdet):

 It's even more surprising for {{{values_list()}}} -- especially for
 {{{values_list( 'field', flat=True)}}}, since it has {{{list}}} in its
 name...

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