Re: [Django] #26607: Add a hook to customize the admin's formsets parameters

[Django]

#26607: Add a hook to customize the admin's formsets parameters
-+-
 Reporter:  David Sanders|Owner:  Manav
 |  Agarwal
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline | Triage Stage:  Accepted
  formset initial|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Manav Agarwal):

 Considering the model and admin as defined below.
 **models.py**

 {{{
 class Author(models.Model):
 name = models.CharField(max_length=100)


 class Book(models.Model):
 author = models.ForeignKey(Author, on_delete=models.CASCADE)
 name = models.CharField(max_length=100)
 }}}
 **admin.py**

 {{{
 class BookInline(admin.StackedInline):
 model = Book
 class AuthorAdmin(admin.ModelAdmin):
 inlines = [
 BookInline,
 ]

 admin.site.register(Author, AuthorAdmin)
 }}}

 Is it a good idea to pass the initial vales of bookinline fields by using
 get request in such a way like
 {{{
 
http://127.0.0.1:8000/admin/polls/author/add/?name=Author_name&book_1_name=book1_name_value&book_2_name=book2_name_value
 }}}
 **Example:**
 {{{
 
http://127.0.0.1:8000/admin/polls/author/add/?name=william_shakespeare&book_1_name=Hamlet&book_2_name=Romeo_and_Juliet
 }}}
 Please update me if the idea seems fine so that I may create a PR in order
 to solve 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.5ce8ad44c6c8eef04f611e1083bfc6d2%40djangoproject.com.

Re: [Django] #26583: Add an option to silence collectstatic clashing files warnings

[Django]

#26583: Add an option to silence collectstatic clashing files warnings
-+-
 Reporter:  Justin McCammon  |Owner:  Ryan
 Type:   |  Hunter
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  2.1
 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 Ryan Hunter):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.3b80ababdb83552a87cce3aa6d605103%40djangoproject.com.

[Django] #32197: Misleading error when loading a database backend fails with ImportError

[Django]

#32197: Misleading error when loading a database backend fails with ImportError
-+-
   Reporter:  Tim|  Owner:  nobody
  Graham |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 For example, in the following case, `django_cockroachdb` is installed but
 has an import error itself.
 {{{
 Traceback (most recent call last):
   File "/home/tim/code/django/django/db/utils.py", line 110, in
 load_backend
 return import_module('%s.base' % backend_name)
   File
 "/home/tim/.virtualenvs/django39/lib/python3.9/importlib/__init__.py",
 line 127, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 1030, in _gcd_import
   File "", line 1007, in _find_and_load
   File "", line 972, in
 _find_and_load_unlocked
   File "", line 228, in
 _call_with_frames_removed
   File "", line 1030, in _gcd_import
   File "", line 1007, in _find_and_load
   File "", line 986, in
 _find_and_load_unlocked
   File "", line 680, in _load_unlocked
   File "", line 790, in exec_module
   File "", line 228, in
 _call_with_frames_removed
   File "/home/tim/code/cockroach-django/django_cockroachdb/__init__.py",
 line 2, in 
 from .lookups import patch_lookups
   File "/home/tim/code/cockroach-django/django_cockroachdb/lookups.py",
 line 1, in 
 from django.db.models.fields.json import HasKeyLookup, KeyTransform
 ModuleNotFoundError: No module named 'django.db.models.fields.json'

 The above exception was the direct cause of the following exception:

 Traceback (most recent call last):
   File "/home/tim/code/mysite/manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/home/tim/code/django/django/core/management/__init__.py", line
 381, in execute_from_command_line
 utility.execute()
   File "/home/tim/code/django/django/core/management/__init__.py", line
 357, in execute
 django.setup()
   File "/home/tim/code/django/django/__init__.py", line 24, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/home/tim/code/django/django/apps/registry.py", line 114, in
 populate
 app_config.import_models()
   File "/home/tim/code/django/django/apps/config.py", line 211, in
 import_models
 self.models_module = import_module(models_module_name)
   File
 "/home/tim/.virtualenvs/django39/lib/python3.9/importlib/__init__.py",
 line 127, in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 1030, in _gcd_import
   File "", line 1007, in _find_and_load
   File "", line 986, in
 _find_and_load_unlocked
   File "", line 680, in _load_unlocked
   File "", line 790, in exec_module
   File "", line 228, in
 _call_with_frames_removed
   File "/home/tim/code/mysite/polls/models.py", line 12, in 
 class Question(models.Model):
   File "/home/tim/code/django/django/db/models/base.py", line 117, in
 __new__
 new_class.add_to_class('_meta', Options(meta, app_label))
   File "/home/tim/code/django/django/db/models/base.py", line 321, in
 add_to_class
 value.contribute_to_class(cls, name)
   File "/home/tim/code/django/django/db/models/options.py", line 204, in
 contribute_to_class
 self.db_table = truncate_name(self.db_table,
 connection.ops.max_name_length())
   File "/home/tim/code/django/django/db/__init__.py", line 28, in
 __getattr__
 return getattr(connections[DEFAULT_DB_ALIAS], item)
   File "/home/tim/code/django/django/db/utils.py", line 201, in
 __getitem__
 backend = load_backend(db['ENGINE'])
   File "/home/tim/code/django/django/db/utils.py", line 121, in
 load_backend
 raise ImproperlyConfigured(
 django.core.exceptions.ImproperlyConfigured: 'django_cockroachdb' isn't an
 available database backend.
 Try using 'django.db.backends.XXX', where XXX is one of:
 'mysql', 'oracle', 'postgresql', 'sqlite3'
 }}}
 I'm not sure there's anything that could be done besides rephrasing the
 error message to say something like this:

  'django_cockroachdb' isn't an available database backend or couldn't be
 imported. Check the above exception.

 In this case, "Try using..." isn't so helpful either. Perhaps we could
 only include that if `backend_name` begins with `django.`.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received

Re: [Django] #32076: Adding async methods to BaseCache

[Django]

#32076: Adding async methods to BaseCache
-+-
 Reporter:  Andrew Chen Wang |Owner:  Andrew
 |  Chen Wang
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  cache| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrew Chen Wang):

 Re-implemented in a new PR without all the extras (I'm sorry about that):
 https://github.com/django/django/pull/13547 I took into account what
 Andrew Godwin said, but I'm a little unclear about what I should actually
 be changing. Are you saying change all the async functions to use
 sync_to_async or how I've currently done it?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/074.e08e4907b4d8128ccc05d4ea631a38d1%40djangoproject.com.

[Django] #32196: bug in admin panel translation when LANGUAGE_CODE is set to anything other than 'en-us'

[Django]

#32196: bug in admin panel translation when LANGUAGE_CODE is set to anything 
other
than 'en-us'
-+-
   Reporter: |  Owner:  nobody
  mh.firouzjah   |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  3.1
  contrib.auth   |   Keywords:
   Severity:  Normal |  auto_translation_error
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hello there
 First of all, I would like to sincerely thank you for your efforts in
 developing Django.
 I am a Persian and I prefer to use Persian language for the site and admin
 panel most of the time; But I noticed that after setting LANGUAGE_CODE for
 Persian, not all texts in the Django admin panel are translated correctly.
 And then I realized that there was a typo in the `locale` files and the
 corresponding text in the Django `Python files`, and that small mistake
 was to use the `Apostrophe character` instead of the `single Quotation
 character`, or vice versa. The inconsistent use of these two characters in
 some cases instead of each other has caused the translations to not be
 done correctly.
 Thank you very much for your attention.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.1a6448f885b17738f13726a74d182794%40djangoproject.com.

Re: [Django] #31026: Switch form rendering to template engine

[Django]

#31026: Switch form rendering to template engine
--+
 Reporter:  Johannes Maron|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Johannes Maron):

 * needs_better_patch:  1 => 0
 * needs_tests:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5f86a73598cf61ced645916ab3b72038%40djangoproject.com.

Re: [Django] #30032: Allow expressions to be used for default

[Django]

#30032: Allow expressions to be used for default
-+-
 Reporter:  Gavin Wahl   |Owner:  Johannes
 |  Maron
 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 Johannes Maron):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8d03143b0a70fa89f49f0e71b1186a1d%40djangoproject.com.

Re: [Django] #31507: Augment QuerySet.exists() optimizations to .union().exists().

[Django]

#31507: Augment QuerySet.exists() optimizations to .union().exists().
-+-
 Reporter:  Simon Charette   |Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   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 David Wobrock):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9b5e4454b1c2af397cd0566044c531aa%40djangoproject.com.

Re: [Django] #32195: Improve error messages from forgetting to call .as_view() on a CBV

[Django]

#32195: Improve error messages from forgetting to call .as_view() on a CBV
---+--
 Reporter:  Angus Holder   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Core (URLs)|  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Description changed by Angus Holder:

Old description:

> We can detect early-on that the user has forgotten to call .as_view() on
> their CBV when passing it into path(). For:
>
> {{{
> urlpatterns = [
> path('home', HomeView)
> ]
> }}}
>
> The error currently happens only when you first load the route (rather
> than when constructing the routes), and looks like
>
> {{{
> Internal Server Error: /
> Traceback (most recent call last):
>   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
> packages\django\core\handlers\exception.py", line 47, in inner
> response = get_response(request)
>   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
> packages\django\core\handlers\base.py", line 179, in _get_response
> response = wrapped_callback(request, *callback_args,
> **callback_kwargs)
> TypeError: __init__() takes 1 positional argument but 2 were given
> }}}
>
> Which is especially hard to work out given that the traceback doesn't
> even include any of the user's own code, and this is an error that's easy
> for beginners to run into when first using CBVs.
>
> My PR changes it to fail early, inside the call to django.urls.path(),
> with a clear error:
>
> {{{
> URL route 'foo' should pass in 'EmptyCBView.as_view()' instead of
> 'EmptyCBView'
> }}}

New description:

 We can detect early-on that the user has forgotten to call .as_view() on
 their CBV when passing it into path(). For:

 {{{
 urlpatterns = [
 path('home', HomeView)
 ]
 }}}

 The error currently happens only when you first load the route (rather
 than when constructing the routes), and looks like

 {{{
 Internal Server Error: /
 Traceback (most recent call last):
   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
 packages\django\core\handlers\exception.py", line 47, in inner
 response = get_response(request)
   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
 packages\django\core\handlers\base.py", line 179, in _get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
 TypeError: __init__() takes 1 positional argument but 2 were given
 }}}

 Which is especially hard to work out given that the traceback doesn't even
 include any of the user's own code, and this is an error that's easy for
 beginners to run into when first using CBVs.

 My PR changes it to fail early, inside the call to django.urls.path(),
 with a clear error:

 {{{
 URL route 'foo' should pass in 'EmptyCBView.as_view()' instead of
 'EmptyCBView'
 }}}

 Pull request: https://github.com/django/django/pull/13682

--

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.47bba77f985b922768aed521567c26ef%40djangoproject.com.

[Django] #32195: Improve error messages from forgetting to call .as_view() on a CBV

[Django]

#32195: Improve error messages from forgetting to call .as_view() on a CBV
-+
   Reporter:  Angus Holder   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Core (URLs)|Version:  3.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+
 We can detect early-on that the user has forgotten to call .as_view() on
 their CBV when passing it into path(). For:

 {{{
 urlpatterns = [
 path('home', HomeView)
 ]
 }}}

 The error currently happens only when you first load the route (rather
 than when constructing the routes), and looks like

 {{{
 Internal Server Error: /
 Traceback (most recent call last):
   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
 packages\django\core\handlers\exception.py", line 47, in inner
 response = get_response(request)
   File "C:\Users\Angus\.virtualenvs\django-WBTbdxDv\lib\site-
 packages\django\core\handlers\base.py", line 179, in _get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
 TypeError: __init__() takes 1 positional argument but 2 were given
 }}}

 Which is especially hard to work out given that the traceback doesn't even
 include any of the user's own code, and this is an error that's easy for
 beginners to run into when first using CBVs.

 My PR changes it to fail early, inside the call to django.urls.path(),
 with a clear error:

 {{{
 URL route 'foo' should pass in 'EmptyCBView.as_view()' instead of
 'EmptyCBView'
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/054.d800fb2d00b7970667cbc7aff6463c5c%40djangoproject.com.

Re: [Django] #27452: Add Postgres serial field to contrib.postgres

[Django]

#27452: Add Postgres serial field to contrib.postgres
-+-
 Reporter:  Johannes Maron   |Owner:
 |  InvalidInterrupt
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  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 Johannes Maron):

 * needs_docs:  0 => 1
 * needs_tests:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0eb67c3c8aa2f13b6260a5a6e3855c24%40djangoproject.com.

Re: [Django] #29010: Allow customizing the autocomplete search results based on the querying model

[Django]

#29010: Allow customizing the autocomplete search results based on the querying
model
-+-
 Reporter:  Muslu Y. |Owner:  Johannes
 |  Hoppe
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignKey,  | Triage Stage:  Accepted
  get_search_results, search_fields  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Johannes Hoppe):

 * needs_better_patch:  1 => 0
 * needs_tests:  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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e688b970d677a9161ab2f83f56976d51%40djangoproject.com.

Re: [Django] #29010: Allow customizing the autocomplete search results based on the querying model

[Django]

#29010: Allow customizing the autocomplete search results based on the querying
model
-+-
 Reporter:  Muslu Y. |Owner:  Johannes
 |  Hoppe
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  ForeignKey,  | Triage Stage:  Accepted
  get_search_results, search_fields  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Johannes Hoppe):

 Ok Carlton, honeymoon's over. I addressed all review comments.

 Gordon, interesting idea, why don't you start a new issue for that, since
 it seems to be a separate 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.66324e03c0f3ddf8c59298ae79973972%40djangoproject.com.

Re: [Django] #31496: Combined queryset crash when chaining `values()` after `order_by()` with annotated constants.

[Django]

#31496: Combined queryset crash when chaining `values()` after `order_by()` with
annotated constants.
-+-
 Reporter:  GardenLee|Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"464a4c0c59277056b5d3c1132ac1b4c6085aee08" 464a4c0c]:
 {{{
 #!CommitTicketReference repository=""
 revision="464a4c0c59277056b5d3c1132ac1b4c6085aee08"
 Fixed #31496 -- Fixed QuerySet.values()/values_list() crash on combined
 querysets ordered by annotations.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ecfd59ebebf4bedc3ce19b1f563ed041%40djangoproject.com.

Re: [Django] #31507: Augment QuerySet.exists() optimizations to .union().exists().

[Django]

#31507: Augment QuerySet.exists() optimizations to .union().exists().
-+-
 Reporter:  Simon Charette   |Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.908dd977e04aabca67282be76c1a1651%40djangoproject.com.

Re: [Django] #31496: Combined queryset crash when chaining `values()` after `order_by()` with annotated constants.

[Django]

#31496: Combined queryset crash when chaining `values()` after `order_by()` with
annotated constants.
-+-
 Reporter:  GardenLee|Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.36faa424586616be35fb0b0cad1c32df%40djangoproject.com.