Re: [Django] #24342: Add EnumField model/form fields

[Django]

#24342: Add EnumField model/form fields
-+-
 Reporter:  Thomas Stephenson|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mahmoud Hossam):

 I'm interested in implementing this feature, but I have a question
 regarding backend support.

 MySQL and PostgreSQL both have native types to support this feature, but
 SQLite and Oracle don't.

 How should we go about supporting this feature on those two databases?

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

Re: [Django] #28524: Improve program name for Django's command-line utility.

[Django]

#28524: Improve program name for Django's command-line utility.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  command-line | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * needs_tests:  1 => 0


Comment:

 Thanks Simon. Test added similar to existing one for `manage.py`; original
 commit referenced.

 There probably ought to be a test for the program name in the help output
 for `django-admin` also, but the test suite executes it from the file path
 directly resulting in `django-admin.py` rather than the documented
 `django-admin`... Not really sure how to get around that.

 What are your thoughts with respect to the other points in this ticket
 about `manage.py`?

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

Re: [Django] #17962: Add ModelAdmin.get_deleted_objects() hook

[Django]

#17962: Add ModelAdmin.get_deleted_objects() hook
---+-
 Reporter:  Chris Wilson   |Owner:  Rebecca Smith
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 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 Rebecca Smith):

 * cc: Rebecca Smith (added)
 * needs_better_patch:  1 => 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/061.08204b9967d1a1c69ba8b301445c1978%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28380: Wrong handling of NULL values in spatialite geometry comparison functions

[Django]

#28380: Wrong handling of NULL values in spatialite geometry comparison 
functions
-+
 Reporter:  Fabian Schindler |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  spatialite geometry  | 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:"da0fb5b1ec89a747459ab64482f3202cb452c068" da0fb5b1]:
 {{{
 #!CommitTicketReference repository=""
 revision="da0fb5b1ec89a747459ab64482f3202cb452c068"
 Fixed #28380 -- Excluded null geometries in SpatiaLite geometry lookups.
 }}}

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

Re: [Django] #28513: LogoutView doesn't support POST, unlike the function-based logout() view

[Django]

#28513: LogoutView doesn't support POST, unlike the function-based logout() view
-+-
 Reporter:  Paulo|Owner:  hui shang
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.11
 Severity:  Release blocker  |   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:"c0f4c60edd429f5ef57241cfabd159d13e26e5ac" c0f4c60e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c0f4c60edd429f5ef57241cfabd159d13e26e5ac"
 Fixed #28513 -- Added POST request support to LogoutView.
 }}}

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

Re: [Django] #28513: LogoutView doesn't support POST, unlike the function-based logout() view

[Django]

#28513: LogoutView doesn't support POST, unlike the function-based logout() view
-+-
 Reporter:  Paulo|Owner:  hui shang
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.11
 Severity:  Release blocker  |   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:"58aaf13e759cf60f8eaab42f650921923fde6502" 58aaf13e]:
 {{{
 #!CommitTicketReference repository=""
 revision="58aaf13e759cf60f8eaab42f650921923fde6502"
 [1.11.x] Fixed #28513 -- Added POST request support to LogoutView.

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

Re: [Django] #28524: Improve program name for Django's command-line utility.

[Django]

#28524: Improve program name for Django's command-line utility.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  command-line | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 > What are your thoughts with respect to the other points in this ticket
 about manage.py?

 About 2. I think it should stay the way it is because while it's invoked
 as `./manage.py` most of the time I've seen `python manage.py` being used
 as well.

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

Re: [Django] #28525: Document GDAL & GeoIP exceptions (was: Add missing documentation for GDAL & GeoIP exceptions)

[Django]

#28525: Document GDAL & GeoIP exceptions
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  gdal geoip geoip2| Triage Stage:  Accepted
  exceptions documentation   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted


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

Re: [Django] #28517: admin does not check if a model has default_permissions before raising PermissionDenied

[Django]

#28517: admin does not check if a model has default_permissions before raising
PermissionDenied
--+
 Reporter:  Paulo |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.11
 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 Tim Graham):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


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

Re: [Django] #28522: Django seems to ignore global DATE_INPUT_FORMATS and TIME_INPUT_FORMATS when set in settings

[Django]

#28522: Django seems to ignore global DATE_INPUT_FORMATS and TIME_INPUT_FORMATS
when set in settings
-+-
 Reporter:  Dan Swain|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  settings | Triage Stage:
  DATE_INPUT_FORMATS |  Unreviewed
  TIME_INPUT_FORMATS forms   |
  validation |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


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

Re: [Django] #28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting

[Django]

#28473: Consider SCRIPT_NAME for SECURE_REDIRECT_EXEMPT setting
---+
 Reporter:  Jonas Haag |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  1.11
 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 Tim Graham):

 * component:  Uncategorized => HTTP handling
 * stage:  Unreviewed => Accepted


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

[Django] #28526: Remedy verbose, often unhelpful undefined tempate variable logging

[Django]

#28526: Remedy verbose, often unhelpful undefined tempate variable logging
+
   Reporter:  Tim Graham|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Template system   |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 As [https://groups.google.com/d/topic/django-
 developers/zdULZcmAWNw/discussion discussed on django-developers], ticket
 #18773 added logging of undefined template variables in Django 1.9
 [dc5b01ad05e50ccde688c73c2ed3334a956076b0], however, I've seen several
 reports of users finding this logging more confusing than helpful. For
 example, [https://groups.google.com/forum/#!topic/django-
 users/6Ve9dcv23sI/discussion admin templates log errors about missing
 is_popup variables] which is how the template are designed (is_popup is
 only in the contexts of pop ups) and the `TECHNICAL_404_TEMPLATE`  (now
 `django/views/templates/technical_404.html`) also logs errors (#26886)
 without any obvious solution about how to prevent that. Also #28516 shows
 the many warnings logged for an admin changelist page.

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

Re: [Django] #26886: TECHNICAL_404_TEMPLATE logs an "Exception while resolving variable" warning

[Django]

#26886: TECHNICAL_404_TEMPLATE logs an "Exception while resolving variable" 
warning
-+-
 Reporter:  None |Owner:  None
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Error reporting  |  Version:  1.9
 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 Tim Graham):

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


Comment:

 I created #28526 to address the problem of verbose, often unhelpful
 logging of undefined variables.

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

Re: [Django] #28516: Admin change_list logs multiple "VariableDoesNotExist" errors.

[Django]

#28516: Admin change_list logs multiple "VariableDoesNotExist" errors.
-+-
 Reporter:  Samuel Bishop|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
  VariableDoesNotExist,  |  Unreviewed
  django.contrib.admin, admin,   |
  template, logging, errors, |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * component:  Template system => contrib.admin
 * resolution:   => duplicate


Comment:

 I created #28526 to address the problem of verbose, often unhelpful
 logging of undefined variables.

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

Re: [Django] #28490: Descriptors on Models are reported as nonexistent by System Check Framework for ModelAdmin.list_display if they return None

[Django]

#28490: Descriptors on Models are reported as nonexistent by System Check 
Framework
for ModelAdmin.list_display if they return None
-+-
 Reporter:  Hunter Richards  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, descriptor,   | Triage Stage:
  system, checks, framework, |  Unreviewed
  validation |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 What's the use case for a descriptor returning `None`?

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

Re: [Django] #28490: Descriptors on Models are reported as nonexistent by System Check Framework for ModelAdmin.list_display if they return None

[Django]

#28490: Descriptors on Models are reported as nonexistent by System Check 
Framework
for ModelAdmin.list_display if they return None
-+-
 Reporter:  Hunter Richards  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, descriptor,   | Triage Stage:
  system, checks, framework, |  Unreviewed
  validation |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Hunter Richards):

 Thanks for the reply, Tim!

 I can't think of a use case for a Descriptor that returns `None` that
 triggers the error reported here, but the Descriptor API makes it very
 easy to shoot yourself in the foot by writing one, and the Python
 Descriptor documentation includes many examples that would trigger this
 error, along with no word on having to manually handle the `if obj is
 None` case (although the `@property` example is correctly written):

 https://docs.python.org/3/howto/descriptor.html

 We initially discovered this bug due to such an improperly written
 Descriptor, and it took us a long time to track down the reason due to the
 triggering of the error message being so deep.  We wanted to save other
 Djangonauts that time in the future!

 Might I also point out that this PR includes a simplification of the
 affected Admin Check code, including the removal of a known code
 duplication, regardless of the prevalence of `None`-returning Descriptors.

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

Re: [Django] #28518: improve performance of loading geometries from DB

[Django]

#28518: improve performance of loading geometries from DB
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  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:"1a85b07bddbf43da00311bdbb3ef5519a3165dc6" 1a85b07]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a85b07bddbf43da00311bdbb3ef5519a3165dc6"
 Fixed #28518 -- Improved performance of loading geometries from DB.
 }}}

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

[Django] #28527: How rewrite query in Django ORM?

[Django]

#28527: How rewrite query in Django ORM?
-+-
   Reporter: |  Owner:  nobody
  mmmcorpsvit|
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  1.11
  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  |
-+-
 has any way to rewrite in Django ORM?

 SELECT * FROM T
 WHERE REPLACE(T.field, '-', ' ') = REPLACE(VALUE,'-', ' ')

 its possible?
 can add this feature or add sample to 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/054.8289ea28e553a4769c66e5df36a8079e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27846: refresh_from_db() doesn't clear reverse OneToOneFields

[Django]

#27846: refresh_from_db() doesn't clear reverse OneToOneFields
-+-
 Reporter:  Keith Hostetler  |Owner:  Paulo
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  refresh_from_db  | Triage Stage:  Accepted
  OneToOneField  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Paulo):

 Hello,
 What do you all think about clearing the fields cache entirely on
 refresh_from_db()?
 This would cover similar bugs where a many to one or many to many
 relationship is cached.
 The only case we can't cover is fields prefetched to custom attributes.

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

Re: [Django] #28527: How rewrite query in Django ORM?

[Django]

#28527: How rewrite query in Django ORM?
-+-
 Reporter:  Nikolas  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.11
  (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 Simon Charette):

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


Comment:

 Hello Nikolas,

 It should be a matter of using `annotate()` with `Func(F('field'),
 function='REPLACE'))`
 [https://docs.djangoproject.com/en/1.11/ref/models/expressions/#func-
 expressions expressions] but I don't think we should be documenting every
 single use of `Func`.

 I suggest you take a look at [how you can get
 
support](https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels)
 if the provided documentation isn't enough to help you solve your issue.

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

Re: [Django] #28527: How rewrite query in Django ORM?

[Django]

#28527: How rewrite query in Django ORM?
-+-
 Reporter:  Nikolas  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.11
  (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
-+-

Comment (by Nikolas):

 i try


 {{{
 obs = Goods.objects\
 .annotate(data2=Func(
 # F('data'),
 F('data'),
 Value("'-'"), Value("' '"),
 function='replace',

 ))\
 .filter(
 Q(data__contains="Andrew") |
 Q(
 data2=Func(
 F('data'),
 Value("'-'"), Value("' '"),
 function='replace',
 ),
 ))
 }}}


 but cant compare to function (not field), this is not documented, can
 litle help please?
 and i think must be more examples in Docs, complex and big examples, very
 need.

 Thanks for great soft!

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

Re: [Django] #27272: Add a on_delete RESTRICT handler to allow cascading deletions while protecting direct ones

[Django]

#27272: Add a on_delete RESTRICT handler to allow cascading deletions while
protecting direct ones
-+-
 Reporter:  Daniel Izquierdo |Owner:  Daniel
 |  Izquierdo
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 Daniel Izquierdo):

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

Re: [Django] #28034: Update the contributing tutorial to use a more recent patch

[Django]

#28034: Update the contributing tutorial to use a more recent patch
-+-
 Reporter:  Mateusz Jankowski|Owner:  Joe
 Type:   |  Krzystan
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 Joe Krzystan):

 * has_patch:  0 => 1


Comment:

 Submitted PR with updates per #5851
 (0034e9af18f3d393a6dd2389ffbba4c919b1d7d7).

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

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