Re: [Django] #26964: No mention of index_together on the GenericForeignKey section

[Django]

#26964: No mention of index_together on the GenericForeignKey section
---+--
 Reporter:  Aidan Lister   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.9
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Daniel Hahler):

 @Aidan:

 > Once we'd resolved that, we noticed a contrib app had no index either
 (django reversion).

 I've created https://github.com/etianen/django-reversion/issues/754 to
 track this - would be good if you could provide more info there, e.g. when
 this is needed/useful.

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

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Vishvajit Pathak):

 Tim

 Current implementation involved just adding the warning message. We are
 not normalizing locale now.

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

Re: [Django] #29754: Trunc() should allow passing is_dst resolution to avoid NonExistentTimeError/AmbiguousTimeError

[Django]

#29754: Trunc() should allow passing is_dst resolution to avoid
NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  Alexander
 |  Holmbäck
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, Trunc, is_dst  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexander Holmbäck):

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

Re: [Django] #29754: Trunc() should allow passing is_dst resolution to avoid NonExistentTimeError/AmbiguousTimeError

[Django]

#29754: Trunc() should allow passing is_dst resolution to avoid
NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  Alexander
 |  Holmbäck
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, Trunc, is_dst  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexander Holmbäck):

 * owner:  nobody => Alexander Holmbäck
 * 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/066.d12e6d040648fdb2bad18b2179a5171c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29758: Document testing custom error handlers

[Django]

#29758: Document testing custom error handlers
-+
   Reporter:  Adam (Chainz) Johnson  |  Owner:  nobody
   Type:  Cleanup/optimization   | Status:  new
  Component:  Documentation  |Version:  2.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 As discussed in #29642, testing custom error handlers is trickier than it
 appears at first sight - to accurately simulate their arguments, it's best
 to actually raise the triggering exceptions, as Django's own test suite
 does:
 
https://github.com/django/django/blob/master/tests/handlers/tests_custom_error_handlers.py#L23

 This could be documented to help users setting out to customize the errors
 Django returns

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

Re: [Django] #29757: Document that easy connect string can be used to connect to pluggable databases on Oracle.

[Django]

#29757: Document that easy connect string can be used to connect to pluggable
databases on Oracle.
--+
 Reporter:  Jani Tiainen  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.1
 Severity:  Normal|   Resolution:
 Keywords:  oracle| 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:  Database layer (models, ORM) => Documentation


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

Re: [Django] #29754: Trunc() should allow passing is_dst resolution to avoid NonExistentTimeError/AmbiguousTimeError

[Django]

#29754: Trunc() should allow passing is_dst resolution to avoid
NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, Trunc, is_dst  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1


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

Re: [Django] #29754: Trunc() should allow passing is_dst resolution to avoid NonExistentTimeError/AmbiguousTimeError (was: Trunc() doesn't handle NonExistentTimeError/AmbiguousTimeError)

[Django]

#29754: Trunc() should allow passing is_dst resolution to avoid
NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, Trunc, is_dst  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * keywords:  pytz, Trunc() => pytz, Trunc, is_dst
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted
 * type:  Bug => New feature


Comment:

 Accepting on the basis that allowing to pass `is_dst=(True|False)` to
 `Trunc` and friends is a feature request analogous to #22598.

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

Re: [Django] #29757: Document that easy connect string can be used to connect to pluggable databases on Oracle. (was: Add simple support for service name as database credentials for Oracle backend)

[Django]

#29757: Document that easy connect string can be used to connect to pluggable
databases on Oracle.
-+-
 Reporter:  Jani Tiainen |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * cc: felixxm (added)
 * stage:  Unreviewed => Accepted
 * type:  New feature => Cleanup/optimization


Comment:

 Maybe a note/example in the
 https://docs.djangoproject.com/en/dev/ref/databases/#id11.

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 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):

 * needs_better_patch:  0 => 1


Comment:

 The patch may need a small change to support "to_tsquery" which is a part
 of [https://github.com/django/django/pull/8491 PR 8491]. Maybe a
 multivalued argument called something like `search_type` with values like
 "raw", "phrase", "plain" would be appropriate.

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

Re: [Django] #29757: Add simple support for service name as database credentials for Oracle backend

[Django]

#29757: Add simple support for service name as database credentials for Oracle
backend
-+-
 Reporter:  Jani Tiainen |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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):

 Apparently there is possibility to use Oracle eazy connect strings as
 well.

 Maybe this could be documented in database spesific documentation?

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

Re: [Django] #26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields

[Django]

#26001: Make ModelAdmin.search_fields do an integer lookup for IntegerFields
-+-
 Reporter:  Tim Graham   |Owner:  Nick
 Type:   |  Sandford
  Cleanup/optimization   |   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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


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

Re: [Django] #29712: Add warning in makemessages command if the localecode with `l` flag is not correct

[Django]

#29712: Add warning in makemessages command if the localecode with `l` flag is 
not
correct
-+-
 Reporter:  Sanyam Khurana   |Owner:  Vishvajit
 Type:   |  Pathak
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


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

Re: [Django] #29754: Trunc() doesn't handle NonExistentTimeError/AmbiguousTimeError

[Django]

#29754: Trunc() doesn't handle NonExistentTimeError/AmbiguousTimeError
-+-
 Reporter:  Alexander Holmbäck   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pytz, Trunc()| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexander Holmbäck):

 Thanks Tim for the valid input, but the situation remains even with dates
 constructed according to pytz documentation, which I hadn't carefully read
 ;-)

 Btw, here's possible solution:
 [https://github.com/django/django/pull/10390 PR].

 If this is a no-go, I think the test
 [https://github.com/django/django/blob/master/tests/admin_views/tests.py#L942
 admin_views.tests.AdminViewBasicTest.test_date_hierarchy_timezone_dst]
 should be changed so that it expects an exception. Otherwise the date
 hierarchy tag is bound to only deal with non-local times (which leads to
 #29724).

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

[Django] #29757: Add simple support for service name as database credentials for Oracle backend

[Django]

#29757: Add simple support for service name as database credentials for Oracle
backend
-+-
   Reporter:  Jani   |  Owner:  nobody
  Tiainen|
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  2.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  oracle
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Oracle 12c with pluggable databases uses service name instead of service
 id (sid) to connect to database if PORT is provided.

 Without port connection uses tnsnames.ora definitions or full DSN string
 in name

 Django code uses only sid when port is defined (3rd parameter of
 {{{makedsn(...)}}} call)

 {{{makedsn(...)}}} call has additional parameter {{{service_name}}} (4th
 parameter)

 It's a bit inconvenient to build full DSN string for connection.

 Sample full DSN string:
 {{{
 
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=foobar)))
 }}}

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

Re: [Django] #29642: Add check for signatures of custom error views

[Django]

#29642: Add check for signatures of custom error views
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   Status:  closed
Component:  Core (System |  Version:  master
  checks)|
 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:"245c36d7b6934fb0ca50eed2414253f4793f1ff5" 245c36d7]:
 {{{
 #!CommitTicketReference repository=""
 revision="245c36d7b6934fb0ca50eed2414253f4793f1ff5"
 Fixed #29642 -- Added check for arguments of custom error handler views.
 }}}

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

Re: [Django] #29642: Add check for signatures of custom error views

[Django]

#29642: Add check for signatures of custom error views
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 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


Comment:

 [https://github.com/django/django/pull/10373 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/068.2f4f16abdcdf5fe86eb024d4148cd8ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29756: Missing information about model field name restriction

[Django]

#29756: Missing information about model field name restriction
---+--
 Reporter:  zdpx   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.1
 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 Tim Graham ):

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


Comment:

 In [changeset:"d483a5f0dc1089ac5caabed0f9b320434d2df723" d483a5f]:
 {{{
 #!CommitTicketReference repository=""
 revision="d483a5f0dc1089ac5caabed0f9b320434d2df723"
 Fixed #29756 -- Doc'd that model field names can't end with an underscore.
 }}}

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

Re: [Django] #897: Bi-Directional ManyToMany in Admin

[Django]

#897: Bi-Directional ManyToMany in Admin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 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 Collin Anderson):

 It can be done with inlines, but not with easy left/right select widget.

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

Re: [Django] #29756: Missing information about model field name restriction (was: Missing information about)

[Django]

#29756: Missing information about model field name restriction
---+--
 Reporter:  zdpx   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  2.1
 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
---+--

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

[Django] #29756: Missing information about

[Django]

#29756: Missing information about
-+
   Reporter:  zdpx   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Documentation  |Version:  2.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Documentation available at
 https://docs.djangoproject.com/en/2.1/topics/db/models/#field-name-
 restrictions says, that there are only 2 restrictions on naming model
 fields:

 1. A field name cannot be a Python reserved word
 2. A field name cannot contain more than one underscore in a row

 I've found another restriction: field name can't ends with underscore,
 because it generates error during making migrations:

 {{{
  (fields.E001) Field names must not end with an underscore.
 }}}

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

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  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:"a4495f4b989dc919d80fcf9f38e31e247faa94fb" a4495f4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="a4495f4b989dc919d80fcf9f38e31e247faa94fb"
 Fixed #29755 -- Made migrations detect changes to
 Meta.default_related_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/070.101482365ba3e61966abb43ed7fe6a93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  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:"4c5a8c6f50577daa8b8aaef28a8f32ab34185e80" 4c5a8c6]:
 {{{
 #!CommitTicketReference repository=""
 revision="4c5a8c6f50577daa8b8aaef28a8f32ab34185e80"
 [2.1.x] Fixed #29755 -- Made migrations detect changes to
 Meta.default_related_name.

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

Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+-
 Reporter:  Dave Hall|Owner:  Arthur
 |  Rio
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  proxy contenttype| Triage Stage:  Accepted
  permission |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: charette.s@… (removed)


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

Re: [Django] #14357: Prevent inappropriate order-based grouping on values+annotate queries

[Django]

#14357: Prevent inappropriate order-based grouping on values+annotate queries
-+-
 Reporter:  Martin Chase |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  3.1  | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * keywords:   => 3.1
 * stage:  Accepted => Someday/Maybe


Comment:

 The behavior change will happen in Django 3.1 when the deprecation ends.

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

Re: [Django] #29711: Add system check to ensure uniqueness of admin actions' __name__.

[Django]

#29711: Add system check to ensure uniqueness of admin actions' __name__.
-+-
 Reporter:  Przemysław   |Owner:
  Buczkowski |  Przemysław Buczkowski
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 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 Carlton Gibson):

 * needs_better_patch:  0 => 1


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

Re: [Django] #14357: Prevent inappropriate order-based grouping on values+annotate queries

[Django]

#14357: Prevent inappropriate order-based grouping on values+annotate queries
-+-
 Reporter:  Martin Chase |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (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 Carlton Gibson):

 * has_patch:  1 => 0


Comment:

 I'm unchecking ''Has patch'', since the PR (deprecating `ordering` being
 used for grouped queries was merged). What remains to close this ticket?

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

Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
-+-
 Reporter:  Dave Hall|Owner:  Arthur
 |  Rio
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  proxy contenttype| Triage Stage:  Accepted
  permission |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Arthur Rio):

 As mentioned on the [https://github.com/django/django/pull/10381 pull
 request], I moved away from my initial comment because:
 1. It's only a temporary fix and we would still need to address the bigger
 issue about how permissions are created for proxy models.
 2. It makes it actually more risky in terms of security as users with
 proxy permissions would suddenly be able to access the admin pages they
 couldn't see before (even though they should have been in the first
 place...)

 I think I'm pretty close to wrapping up the code changes and I'd love some
 feedback before I start writing up the docs and the release notes. You can
 check the [https://github.com/django/django/pull/10381 pull request] for
 more details about the current state of things and how this patch would
 impact permissions.

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

Re: [Django] #29755: Infinite migrations created after removing Meta.default_related_name

[Django]

#29755: Infinite migrations created after removing Meta.default_related_name
-+-
 Reporter:  Aamir Rind   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
  migrations,unlimited,infinite,makemigrations|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 Yep. Looks good.

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