Re: [Django] #30064: Admin search with a null character crashes with "A string literal cannot contain NUL (0x00) characters." on PostgreSQL (was: Inputting search-query with null character to browser

[Django]

#30064: Admin search with a null character crashes with "A string literal cannot
contain NUL (0x00) characters." on PostgreSQL
---+
 Reporter:  kenichi-cc |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.1
 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):

 * stage:  Unreviewed => Accepted


Comment:

 This is related to #28201. The exception was
 [https://github.com/psycopg/psycopg2/issues/420 introduced in psycopg2
 2.7+].

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

[Django] #30064: Inputting search-query with null character to browser URL field and crash

[Django]

#30064: Inputting search-query with null character to browser URL field and 
crash
-+
   Reporter:  kenichi-cc |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |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  |
-+
 1. Input following URL to browser URL field and access.

 http://localhost/admin/auth/user/?q=%00

 2. Crash with following Error.

 {{{
 Environment:


 Request Method: GET
 Request URL: http://localhost/admin/auth/user/?q=%00

 Django Version: 2.1.4
 Python Version: 3.6.7
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.messages',
  'django.contrib.staticfiles',
  'django_extensions',
  'rest_framework',
  'select2',
  'corsheaders',
  ...]
 Installed Middleware:
 ['django.middleware.security.SecurityMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'corsheaders.middleware.CorsMiddleware',
  'django.middleware.common.CommonMiddleware',
  'django.middleware.csrf.CsrfViewMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.contrib.messages.middleware.MessageMiddleware',
  'django.middleware.clickjacking.XFrameOptionsMiddleware']



 Traceback:

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/core/handlers/exception.py" in inner
   34. response = get_response(request)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/core/handlers/base.py" in _get_response
   126. response = self.process_exception_by_middleware(e,
 request)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/core/handlers/base.py" in _get_response
   124. response = wrapped_callback(request,
 *callback_args, **callback_kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/options.py" in wrapper
   604. return self.admin_site.admin_view(view)(*args,
 **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/utils/decorators.py" in _wrapped_view
   142. response = view_func(request, *args, **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/views/decorators/cache.py" in _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/sites.py" in inner
   223. return view(request, *args, **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/utils/decorators.py" in _wrapper
   45. return bound_method(*args, **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/utils/decorators.py" in _wrapped_view
   142. response = view_func(request, *args, **kwargs)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/options.py" in changelist_view
   1675. cl = self.get_changelist_instance(request)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/options.py" in get_changelist_instance
   742. sortable_by,

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/views/main.py" in __init__
   81. self.get_results(request)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/contrib/admin/views/main.py" in get_results
   209. result_count = paginator.count

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/utils/functional.py" in __get__
   37. res = instance.__dict__[self.name] = self.func(instance)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/core/paginator.py" in count
   87. return self.object_list.count()

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/db/models/query.py" in count
   383. return self.query.get_count(using=self.db)

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/db/models/sql/query.py" in get_count
   498. number = obj.get_aggregation(using, ['__count'])['__count']

 File "/root/.pyenv/versions/3.6.7/envs/app/lib/python3.6/site-
 packages/django/db/models/sql/query.py" in get_aggregation
   483. result = 

Re: [Django] #29111: Use autocomplete_fields in list_filter for related models

[Django]

#29111: Use autocomplete_fields in list_filter for related models
---+
 Reporter:  Paul Tiplady   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  2.0
 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 Christophe Baldy):

 * cc: Christophe Baldy (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/069.0b120853550868324e8ddd99af9edd38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28369: Provide ModelAdmin hooks for reversing URLs

[Django]

#28369: Provide ModelAdmin hooks for reversing URLs
---+
 Reporter:  steve yeago|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Christophe Baldy):

 * cc: Christophe Baldy (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/063.5dc0f552663d0914a9e48110831c4ee1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29994: Document performance issues in FileBasedCache

[Django]

#29994: Document performance issues in FileBasedCache
--+
 Reporter:  Mateusz Konieczny |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.1
 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 Grant Jenks):

 I looked at the patch in #11260 but as far as I can tell it only adds a
 scenario where when `_max_enries` is set to 0 or None then no culling ever
 takes place. I'm not sure how `anteater_sa` handles cache size in that
 case. I suppose if you can guarantee that the filesystem cache will never
 grow beyond a certain size then that's a reasonable strategy. It's more of
 a persistent dictionary though.

 I certainly think filesystem caching has serious use cases. I myself have
 used diskcache for an ecommerce site for several years with tens of
 thousands of pages. I started with the built-in file-based cached but
 later chose sqlite3 (used by diskcache) for better performance.

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

Re: [Django] #30062: Add UniqueConstraint condition parameter

[Django]

#30062: Add UniqueConstraint condition parameter
-+-
 Reporter:  Pavel Tyslacki   |Owner:  nobody
 Type:  New feature  |   Status:  new
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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

Re: [Django] #30063: Document that unique_together might be deprecated in favor of constraints in the future.

[Django]

#30063: Document that unique_together might be deprecated in favor of 
constraints
in the future.
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

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

Re: [Django] #29850: Add window support for RowRange frames

[Django]

#29850: Add window support for RowRange frames
-+-
 Reporter:  Daniel Fuchs |Owner:  Bryan
 |  Collazo
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  2.1 => master


Old description:

> The current RowRange frame is missing handling for several cases.
>
> None of the following are currently supported:
> RowRange(start=-2, end=-1)
> ROWS BETWEEN 2 PRECEDING AND 1 PRECEDING
> RowRange(start=1, end=2)
> ROWS BETWEEN 1 FOLLOWING AND 2 FOLLOWING
>
> It's also missing support for EXCLUDE.
> ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING EXCLUDE CURRENT ROW

New description:

 The current RowRange frame is missing handling for several cases.

 None of the following are currently supported:
 RowRange(start=-2, end=-1)
 ROWS BETWEEN 2 PRECEDING AND 1 PRECEDING
 RowRange(start=1, end=2)
 ROWS BETWEEN 1 FOLLOWING AND 2 FOLLOWING

 It's also missing support for EXCLUDE.
 ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING EXCLUDE CURRENT ROW

 

 Frame exclusion is supported only in [https://www.postgresql.org/docs/11
 /sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS PostgreSQL 11+], other
 databases do not support exclusion (see
 [https://docs.oracle.com/en/database/oracle/oracle-database/18/sqlrf
 /Analytic-Functions.html#GUID-527832F7-63C0-4445-8C16-307FA5084056 Oracle
 18c doc], [https://mariadb.com/kb/en/library/window-functions-overview/
 MariaDB doc], and [https://dev.mysql.com/doc/refman/8.0/en/window-
 functions-frames.html MySQL doc]).

--

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

Re: [Django] #29851: Window Frame Doesn't Work In SubQuery

[Django]

#29851: Window Frame Doesn't Work In SubQuery
-+-
 Reporter:  Daniel Fuchs |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Window   | 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 GitHub ):

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


Comment:

 In [changeset:"dd8ed64113947ed066b83e443053e389e8f77ebc" dd8ed64]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd8ed64113947ed066b83e443053e389e8f77ebc"
 Fixed #29851 -- Fixed crash of annotations with window expressions in
 Subquery.
 }}}

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

Re: [Django] #29619: Raised FieldError's should include the field that caused the error

[Django]

#29619: Raised FieldError's should include the field that caused the error
-+-
 Reporter:  Alex Hayes   |Owner:  Jeff
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 The new PR also requires adjustments.

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

Re: [Django] #28690: django.utils.http.parse_http_date two digit year check is incorrect

[Django]

#28690: django.utils.http.parse_http_date two digit year check is incorrect
-+--
 Reporter:  Mads Jensen  |Owner:  Tameesh Biswas
 Type:  Bug  |   Status:  assigned
Component:  Utilities|  Version:  master
 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 Simon Charette):

 Tameesh, I left a comment on the PR regarding the use of non-UTC
 ''today''.

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

Re: [Django] #27080: `as_manager` on QuerySet should pass down `use_in_migrations` to new Manager instance

[Django]

#27080: `as_manager` on QuerySet should pass down `use_in_migrations` to new
Manager instance
-+-
 Reporter:  Leif Denby   |Owner:  Oliver Newman
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  0 => 1


Comment:

 PR still needs to test migration serialization of querysets or queryset
 generated managers.

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

Re: [Django] #30024: The test client request methods should raise an error when passed None as a data value

[Django]

#30024: The test client request methods should raise an error when passed None 
as a
data value
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  master
 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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"6fe9c45b725cd21eacbb50263bd3449e1a3edf17" 6fe9c45b]:
 {{{
 #!CommitTicketReference repository=""
 revision="6fe9c45b725cd21eacbb50263bd3449e1a3edf17"
 Fixed #30024 -- Made urlencode() and Client raise TypeError when None is
 passed as data.
 }}}

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

Re: [Django] #30062: Add UniqueConstraint condition parameter

[Django]

#30062: Add UniqueConstraint condition parameter
-+-
 Reporter:  Pavel Tyslacki   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  1 => 0


Old description:

> According [https://code.djangoproject.com/ticket/29641] and
> [https://code.djangoproject.com/ticket/29547] add support of conditional
> unique constraint.
>
> Postgresql and sqlite support it as unique index: `CREATE UNIQUE INDEX
> ... WHERE condition`, for unsupported databases this constraint will not
> be applied at all.

New description:

 According #29641 and #29547, add support of conditional unique constraint.

 Postgresql and sqlite support it as unique index: `CREATE UNIQUE INDEX ...
 WHERE condition`, for unsupported databases this constraint will not be
 applied at all.

--

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

Re: [Django] #29851: Window Frame Doesn't Work In SubQuery

[Django]

#29851: Window Frame Doesn't Work In SubQuery
-+-
 Reporter:  Daniel Fuchs |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Window   | 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/065.a44bf2c3d662b314732de13a2ab6e1b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17522: ModelAdmin.ordering validation too strict

[Django]

#17522: ModelAdmin.ordering validation too strict
-+-
 Reporter:  Sebastian Goll   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, validation,   | Triage Stage:  Accepted
  ordering, strict   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Kevin Christopher Henry):

 > If you are dynamically defining an annotation then why are you not
 dynamically ordering by this annotation and expecting static options to
 work with it?

 I'm expecting it because that's how `list_display` works. The purpose of
 `admin_order_field` is to allow you to ''statically declare'' how to order
 a ''dynamic'' piece of code. Given that this exists, it seems wrong not to
 respect it when it comes to the `ordering` attribute.

 To me, the bug isn't about how much you can or can't declare statically,
 it's about making the API more consistent. I haven't looked at the
 proposed patch, but I think this general idea - considering
 `admin_order_field` when looking at `ordering` - will be an improvement.

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

Re: [Django] #30049: GIS widgets don't initialize properly after clicking "Add another" in admin inlines

[Django]

#30049: GIS widgets don't initialize properly after clicking "Add another" in 
admin
inlines
--+
 Reporter:  Lars Solberg  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  GIS   |  Version:  2.1
 Severity:  Normal|   Resolution:
 Keywords:  gis, admin| 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):

 * Attachment "t30049.zip" added.

 sample app to reproduce

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

Re: [Django] #30049: GIS widgets don't initialize properly after clicking "Add another" in admin inlines (was: Multiple problems using gis fields in admin inlines)

[Django]

#30049: GIS widgets don't initialize properly after clicking "Add another" in 
admin
inlines
--+
 Reporter:  Lars Solberg  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  GIS   |  Version:  2.1
 Severity:  Normal|   Resolution:
 Keywords:  gis, admin| 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):

 * stage:  Unreviewed => Accepted


Comment:

 Using the attached sample project, I can reproduce the problem that
 clicking  "Add another City" on the admin's state change form doesn't
 initialize the new widget properly (textarea instead of the openlayers
 widget). It doesn't seem to be a new issue -- I reproduced back as far as
 I tested (Django 1.11).

 I'm not sure if the "missing elements in the upper right corner" part of
 this report is valid... when using `PointField` in a non-inline admin,
 those elements don't appear either. Are they not applicable to
 `PointField`? In any case, a bug report should be limited to one issue so
 let's keep this ticket limited to the "Add another" initialization and
 open addition tickets if more issues remain.

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

Re: [Django] #30059: DELETE request with payload makes subsequent request fail

[Django]

#30059: DELETE request with payload makes subsequent request fail
---+--
 Reporter:  diurchenko |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  2.1
 Severity:  Normal |   Resolution:  needsinfo
 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:   => needsinfo
 * component:  Uncategorized => HTTP handling
 * type:  Uncategorized => Bug


Comment:

 In any case, I think we need a test or some some sample code reproduce the
 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/068.91e0b63a464a98656d0afae7adabe0b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #15015: Mixing read-only with ability to add new instances using a FormSet

[Django]

#15015: Mixing read-only with ability to add new instances using a FormSet
-+
 Reporter:  coleifer |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  formset  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Sergey Fedoseev):

 * cc: Sergey Fedoseev (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.9bba8a080dd02c947a9f760ec9e2b604%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.