Re: [Django] #34380: Make URLField assume "https".

[Django]

#34380: Make URLField assume "https".
-+-
 Reporter:  Coen van der Kamp|Owner:  Coen van
 Type:   |  der Kamp
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  4.1
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"92af3d4d235448446e53e982275315bedcc4c204" 92af3d4d]:
 {{{
 #!CommitTicketReference repository=""
 revision="92af3d4d235448446e53e982275315bedcc4c204"
 [5.0.x] Refs #34380 -- Added FORMS_URLFIELD_ASSUME_HTTPS transitional
 setting.

 This allows early adoption of the new default "https".

 Backport of a4931cd75a1780923b02e43475ba5447df3adb31 from main.
 }}}

-- 
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/0107018c1755e03b-23d9df0a-c724-40e8-8162-58fbc1969910-00%40eu-central-1.amazonses.com.

Re: [Django] #34380: Make URLField assume "https".

[Django]

#34380: Make URLField assume "https".
-+-
 Reporter:  Coen van der Kamp|Owner:  Coen van
 Type:   |  der Kamp
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  4.1
 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
-+-

Comment (by GitHub ):

 In [changeset:"a4931cd75a1780923b02e43475ba5447df3adb31" a4931cd7]:
 {{{
 #!CommitTicketReference repository=""
 revision="a4931cd75a1780923b02e43475ba5447df3adb31"
 Refs #34380 -- Added FORMS_URLFIELD_ASSUME_HTTPS transitional setting.

 This allows early adoption of the new default "https".
 }}}

-- 
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/0107018c17518432-17fc527a-f531-450e-9c4d-db872587702c-00%40eu-central-1.amazonses.com.

Re: [Django] #34998: Raising a StopIteration in asynchronous mode hangs the request

[Django]

#34998: Raising a StopIteration in asynchronous mode hangs the request
-+-
 Reporter:  Clément Escolano |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  4.2
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  Uncategorized => Core (Other)
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Thanks for comments!

 Closing as "wontfix" unless someone can prove it's actionable in Django
 itself.

-- 
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/0107018c175000c5-ecb31efc-50b3-4bc6-bae2-5d21ed36a03b-00%40eu-central-1.amazonses.com.

Re: [Django] #34998: Raising a StopIteration in asynchronous mode hangs the request

[Django]

#34998: Raising a StopIteration in asynchronous mode hangs the request
--+--
 Reporter:  Clément Escolano  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  Uncategorized |  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Andrew Godwin):

 Hmm yes, this is one of those nasty bugs that reveals the true nature of
 how Python async works.

 In testing this locally with just plain async functions, I don't see how
 we can catch this - the error happens when you return StopIteration from
 _any_ awaited function, you can't wrap around it to catch it instead.
 Given that views are always going to be async functions, unless we want to
 wrap every single view, decorator and middleware in our own custom Future
 it's not going to be reasonable to catch 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/0107018c174c7d43-fc6f32f6-c109-4c27-a517-0f6a0705df2d-00%40eu-central-1.amazonses.com.

Re: [Django] #34998: Raising a StopIteration in asynchronous mode hangs the request

[Django]

#34998: Raising a StopIteration in asynchronous mode hangs the request
--+--
 Reporter:  Clément Escolano  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  Uncategorized |  Version:  4.2
 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
--+--
Changes (by Carlton Gibson):

 * cc: Andrew Godwin (added)


Comment:

 Good issue. AFAICS this is https://github.com/python/cpython/issues/112182

 See also https://github.com/agronholm/anyio/pull/477 and
 https://github.com/tiangolo/fastapi/issues/966 — aynio was able to work
 around it, but it's not clear we're going to be able to doing anything
 pending a fix in asyncio.

 To quote Guido from the Python issue:

 > My first response is "don't do that". That's why it prints such an
 elaborate warning.

 Short of a concrete suggestion, 路‍♀️

-- 
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/0107018c1742b334-b6320e5f-96f8-41e5-8f5b-6033023e49c0-00%40eu-central-1.amazonses.com.

Re: [Django] #28586: Automatically prefetch related for "to one" fields as needed.

[Django]

#28586: Automatically prefetch related for "to one" fields as needed.
-+-
 Reporter:  Gordon Wrigley   |Owner:  Adam
 |  Johnson
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch_related | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Adam Johnson):

 * owner:  nobody => Adam Johnson
 * needs_docs:  1 => 0
 * has_patch:  1 => 0
 * status:  new => assigned


Comment:

 I’m working on a PR for Django core now, based on
 [https://github.com/django/django/pull/16090/files Andreas Pelme’s
 recently-closed PR] and discussions with Andreas and Simon Charette.

-- 
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/0107018c17008b60-db02e0c9-01a2-4e0c-94b6-402bf80816f4-00%40eu-central-1.amazonses.com.

Re: [Django] #34262: Queryset grouped by annotation with aggregates on another annotated expression crashes on MySQL with sql_mode=only_full_group_by.

[Django]

#34262: Queryset grouped by annotation with aggregates on another annotated
expression crashes on MySQL with sql_mode=only_full_group_by.
-+-
 Reporter:  Mariusz Felisiak |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:  Accepted
  only_full_group_by |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 FWIW this relates to #34992 where we had to disable
 `allows_group_by_selected_pks` on MariaDB entirely as it doesn't implement
 any form of functional dependence resolition.

-- 
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/0107018c16c9cd5f-48d3d006-a26a-44a0-82e9-eba26c8af697-00%40eu-central-1.amazonses.com.

Re: [Django] #34998: Raising a StopIteration in asynchronous mode hangs the request

[Django]

#34998: Raising a StopIteration in asynchronous mode hangs the request
--+--
 Reporter:  Clément Escolano  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  Uncategorized |  Version:  4.2
 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
--+--
Changes (by Mariusz Felisiak):

 * cc: Carlton Gibson (added)


Comment:

 Is it not a duplicate of #33795, #32798, or #33735?

-- 
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/0107018c16c7e96e-ac77ef0b-b01a-455e-9b6f-798d111e686a-00%40eu-central-1.amazonses.com.

Re: [Django] #27676: MariaDB 10.2 supports defaults for text columns

[Django]

#27676: MariaDB 10.2 supports defaults for text columns
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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:  new => closed
 * resolution:   => fixed


Comment:

 Please open a new ticket rather than reopening an old one.

-- 
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/0107018c16599cd1-cbdd4c6e-38b9-4c56-abc6-12f4e29a8a45-00%40eu-central-1.amazonses.com.

Re: [Django] #27676: MariaDB 10.2 supports defaults for text columns

[Django]

#27676: MariaDB 10.2 supports defaults for text columns
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (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 Tobias Krönke):

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


Comment:

 PR added: https://github.com/django/django/pull/17539

-- 
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/0107018c1646db7d-503d935f-f5bf-43d3-a99e-117e8eedae40-00%40eu-central-1.amazonses.com.

Re: [Django] #28800: Add a management command to list URL patterns

[Django]

#28800: Add a management command to list URL patterns
-+-
 Reporter:  Martín Peveri|Owner:  Xavier
 |  Tilley
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 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 Natalia Bidart):

 Discussion in the forum where consensus seems quite clear:
 https://forum.djangoproject.com/t/should-the-show-urls-command-be-part-of-
 djangos-standard-library/20739

-- 
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/0107018c162cf70a-ff3c6422-25f1-4ddd-a8f5-283b14cb68a5-00%40eu-central-1.amazonses.com.

[Django] #34998: Raising a StopIteration in asynchronous mode hangs the request

[Django]

#34998: Raising a StopIteration in asynchronous mode hangs the request
+
   Reporter:  Clément Escolano  |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  Uncategorized |Version:  4.2
   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 |
+
 When using Django in Asynchronous mode, if some code raises a
 `StopIteration` error (generally when calling `next()` on an empty
 generator), the request hangs. I think Django should handle the error
 gracefully (display a 500 error page) instead.

 Basically, when the code raises a `StopIteration` error, the following is
 displayed and the request hangs:

 {{{
 TypeError: StopIteration interacts badly with generators and cannot be
 raised into a Future
 }}}

 I have reproduce the issue with a minimal project here: https://github.com
 /clement-escolano/django-stopiteration

 Relevant file is `stopiteration/views.py` which is a view called on
 `/error` endpoint and contains:

 {{{
 def error(request):
 next(i for i in [])
 return None
 }}}

 The Django application must be run with asynchronous support. For instance
 with: `uvicorn test_stopiteration.asgi:application`.

-- 
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/0107018c1617ddbb-85f9e517-17ca-487f-a424-9e137085a93f-00%40eu-central-1.amazonses.com.

Re: [Django] #34986: Fix up support for PyPy 3.10

[Django]

#34986: Fix up support for PyPy 3.10
--+-
 Reporter:  Nick Pope |Owner:  Nick Pope
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  pypy  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5f9e5c1b0d5680f793ba7646d52ffab9e2c3623f" 5f9e5c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="5f9e5c1b0d5680f793ba7646d52ffab9e2c3623f"
 Refs #34822, Refs #34986 -- Fixed migrations serializer support for
 functools.lru_cache().

 It turns out that `functools._lru_cache_wrapper` is only a class when
 CPython's _functools C module provides it, otherwise it is a function.
 PyPy also provides it as a function.
 }}}

-- 
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/0107018c15f8f77c-c8e4f9c1-9f8b-4156-b55d-a5da81acd5c4-00%40eu-central-1.amazonses.com.

Re: [Django] #34822: Provide migration serializer for `_lru_cache_wrapper`

[Django]

#34822: Provide migration serializer for `_lru_cache_wrapper`
-+-
 Reporter:  Natalia Bidart   |Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  serializer   | Triage Stage:  Ready for
  functools cache|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5f9e5c1b0d5680f793ba7646d52ffab9e2c3623f" 5f9e5c1]:
 {{{
 #!CommitTicketReference repository=""
 revision="5f9e5c1b0d5680f793ba7646d52ffab9e2c3623f"
 Refs #34822, Refs #34986 -- Fixed migrations serializer support for
 functools.lru_cache().

 It turns out that `functools._lru_cache_wrapper` is only a class when
 CPython's _functools C module provides it, otherwise it is a function.
 PyPy also provides it as a function.
 }}}

-- 
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/0107018c15f8f7af-980241fc-e048-4ccb-838a-0bf05bec43c6-00%40eu-central-1.amazonses.com.

Re: [Django] #33174: Having a model inherit from Generic[T] breaks makemigrations

[Django]

#33174: Having a model inherit from Generic[T] breaks makemigrations
+--
 Reporter:  Antoine Humeau  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  Migrations  |  Version:  3.2
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Adam Johnson):

 I would be inclined to agree. Have you looked into what it would take to
 support `Generic`, Jacob? I would hope the patch is pretty small.

-- 
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/0107018c1595c4e5-bac8bffd-b7d4-4d3b-a087-5198084381ce-00%40eu-central-1.amazonses.com.

Re: [Django] #27676: MariaDB 10.2 supports defaults for text columns

[Django]

#27676: MariaDB 10.2 supports defaults for text columns
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tobias Krönke):

 Could we skip the default if it's the empty string for MySQL? Explicitly
 setting the empty string prevents the `ALGORITHM=INSTANT` magic from
 adding the column without table copying. This would be a huge performance
 improvement for many users. I have seen so many issues where people would
 like to add new columns to very large tables efficiently. MySQL has this
 now built-in, but django prevents it by redudantly specifying the empty
 string as default. This is enough and makes the instant algorithm work:

 {{{
 ALTER TABLE `` ADD COLUMN `` longtext NOT NULL;
 }}}


 Same for CHAR and VARCHAR.

-- 
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/0107018c1593e0c8-a6240b1a-26b9-4bc3-bdf0-12a50ccb87fb-00%40eu-central-1.amazonses.com.

Re: [Django] #21442: Configurable request parsing.

[Django]

#21442: Configurable request parsing.
---+--
 Reporter:  Tom Christie   |Owner:  Carlton Gibson
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Mariusz Felisiak ):

 In [changeset:"76280b4f4d7547dc869b71c22f658095a1565875" 76280b4f]:
 {{{
 #!CommitTicketReference repository=""
 revision="76280b4f4d7547dc869b71c22f658095a1565875"
 Refs #21442 -- Increased test coverage of requests.
 }}}

-- 
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/0107018c155e4fa2-80d8714c-aa1c-42a0-a64c-864b2b9711b0-00%40eu-central-1.amazonses.com.

Re: [Django] #28822: Add DBCalculatedField to model to annotate models automatically

[Django]

#28822: Add DBCalculatedField to model to annotate models automatically
-+-
 Reporter:  Ilya |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => duplicate
 * stage:  Accepted => Unreviewed


Comment:

 Closing as a duplicate of #31300.

-- 
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/0107018c151ba07a-2b5d5231-3e4c-486e-8e10-7fdc349af0d0-00%40eu-central-1.amazonses.com.

Re: [Django] #28822: Add DBCalculatedField to model to annotate models automatically

[Django]

#28822: Add DBCalculatedField to model to annotate models automatically
-+-
 Reporter:  Ilya |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (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
-+-

Comment (by Tom Carrick):

 This looks very similar to the new GeneratedField - is there still some
 value here?

-- 
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/0107018c151aaa7d-df9599df-ca11-4724-8f31-38481d0d6a04-00%40eu-central-1.amazonses.com.

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  Moses
 |  Mugisha
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tom Carrick):

 * cc: Tom Carrick (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018c15159a11-7e683925-1e92-4fba-a3ee-cf4cdbdee776-00%40eu-central-1.amazonses.com.

Re: [Django] #28800: Add a management command to list URL patterns

[Django]

#28800: Add a management command to list URL patterns
-+-
 Reporter:  Martín Peveri|Owner:  Xavier
 |  Tilley
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 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 Tom Carrick):

 This looks very similar to the new `GeneratedField` - is there still some
 value here?

-- 
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/0107018c15143bef-26261ba1-6583-4dca-8924-4ea65227c47d-00%40eu-central-1.amazonses.com.