[Django] #30724: Please create a hyperlink to easy pickings in README.rst file

[Django]

#30724: Please create a hyperlink to easy pickings in README.rst  file
-+-
   Reporter:  Srinivas   |  Owner:  nobody
  Reddy Thatiparthy  |
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  2.2
  Documentation  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I think it is high time we include the hyperlink to "easy pickings"
 issues.  This encourages newbies to contribute to Django project.

-- 
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/056.578ddf6c3b0d0d470201ca05eb4cc6dd%40djangoproject.com.

Re: [Django] #27747: Add signals for Django management commands

[Django]

#27747: Add signals for Django management commands
-+-
 Reporter:  Dmitry Gladkov   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Matthew Schinckel):

 The one I have in mind is being able to fire off a seperate process when
 starting `runserver` (for instance, to make sure that our JS build pathway
 stuff has a "watch" server running).

-- 
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/061.b0ca2b4974465a102c282820ee2bbd7d%40djangoproject.com.

Re: [Django] #30723: Lazy translations in field help cause JSON serialize errors

[Django]

#30723: Lazy translations in field help cause JSON serialize errors
-+-
 Reporter:  Rob Lineberger   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.auth |  Version:  2.2
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:  json lazy| Triage Stage:
  serialization  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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


Comment:

 Django has a special JSON encoder to dumps typical Django data:
 https://docs.djangoproject.com/en/2.2/topics/serialization/#djangojsonencoder
 I don't see what we could do to prevent your bad debugging session, but if
 you have ideas, feel free to suggest them.

-- 
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/065.ab1221b949ebc11e1bd645b1b22c3441%40djangoproject.com.

[Django] #30723: Lazy translations in field help cause JSON serialize errors

[Django]

#30723: Lazy translations in field help cause JSON serialize errors
-+-
   Reporter:  Rob|  Owner:  nobody
  Lineberger |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  2.2
  contrib.auth   |   Keywords:  json lazy
   Severity:  Normal |  serialization
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Attempting to json.dumps() the result of apps.get_models() leads to a
 TypeError:

 {{{

 TypeError at /uploader/select-models/

 'Designates whether this user should be treated as active. Unselect this
 instead of deleting accounts.' is not JSON serializable
 }}}

 That is because "Designates whether this user should be treated as active.
 " is not a string, but the converted representation of a
 django.utils.functional.lazy.__proxy__ object.  That is not JSON
 serializable.

 Debugging this is onerous because in all respects the help text looks and
 acts like a string.

-- 
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/050.5e6c3dda4b4712bec1e495887fe530a2%40djangoproject.com.

Re: [Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
 Reporter:  Federico Jaramillo   |Owner:  nobody
  Martínez   |
 Type:   |   Status:  new
  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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * stage:  Unreviewed => Accepted


Comment:

 I cannot say for sure 500 is the good value, but some delay is definitely
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.df57010afdbe94a46021c4e87c15e1e1%40djangoproject.com.

Re: [Django] #30721: Implicit related objects filtration because of the set Manager.

[Django]

#30721: Implicit related objects filtration because of the set Manager.
-+-
 Reporter:  ApaDoctor|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * component:  Uncategorized => Database layer (models, ORM)
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 Thanks for the report, IMO everything works properly, let's analyze this
 step by step.

 You inherited from `SomeAbstractModel` with a manager and define a
 `custom_manager` in `SomeThing`. `custom_manager` is a default manager for
 `SomeThing` that's why it's used by related manager (e.g. `x.children`).
 In the same time `SomeThing` inherited `objects` manager from
 `SomeAbstractModel` (it's no longer a default manager provided by Django,
 see [https://docs.djangoproject.com/en/2.2/topics/db/managers/#manager-
 names manager-names]) so when you call it explicit e.g.
 `SomeThing.objects.filter(parent_id=1).count()` it returns all rows,
 without an extra filter (see also
 [https://docs.djangoproject.com/en/2.2/topics/db/managers/#custom-
 managers-and-model-inheritance custom-managers-and-model-inheritance] and
 [https://docs.djangoproject.com/en/2.2/topics/db/queries/#using-a-custom-
 reverse-manager using-a-custom-reverse-manager]).

-- 
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.253772dcc0c1ed67a0195c573321aa12%40djangoproject.com.

Re: [Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
 Reporter:  Federico Jaramillo   |Owner:  nobody
  Martínez   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 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:  0
-+-
Changes (by Federico Jaramillo Martínez):

 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization


Old description:

> The current implementation of the Ajax autocomplete widget using Select2
> in Django triggers a request for every key-press. This creates
> unnecessary load on servers.
>
> This patch rate-limit the requests by adding a delay using the
> `ajax.delay` option provided by Select2.

New description:

 The current implementation of the Ajax autocomplete widget using Select2
 in Django triggers a request for every key-press. This creates unnecessary
 load on servers.

 This patch rate-limit the requests by adding a delay using the
 `ajax.delay` option provided by Select2.

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

--

Comment:

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

Re: [Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
 Reporter:  Federico Jaramillo   |Owner:  nobody
  Martínez   |
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  master
 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 Federico Jaramillo Martínez):

 * Attachment "no-rate-limit.mp4" added.

 Multiple consecutive request

-- 
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.bf877aca56e2bbfe7bc0b38d62387e2e%40djangoproject.com.

Re: [Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
 Reporter:  Federico Jaramillo   |Owner:  nobody
  Martínez   |
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  master
 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 Federico Jaramillo Martínez):

 * Attachment "with-rate-limit.mp4" added.

 Requests with a delay until user stops typing

-- 
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.5a3c7ab93b29c8980a57dcc7af01974e%40djangoproject.com.

[Django] #30722: Rate-limit autocomplete widgets Ajax requests

[Django]

#30722: Rate-limit autocomplete widgets Ajax requests
-+-
   Reporter:  Federico   |  Owner:  nobody
  Jaramillo Martínez |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  master
  contrib.admin  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The current implementation of the Ajax autocomplete widget using Select2
 in Django triggers a request for every key-press. This creates unnecessary
 load on servers.

 This patch rate-limit the requests by adding a delay using the
 `ajax.delay` option provided by Select2.

-- 
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/053.315dcc6dc7dd4e7812743b5d6e633eb0%40djangoproject.com.

Re: [Django] #30720: allow specifying multiple domains for makemessages and compilemessages commands

[Django]

#30720: allow specifying multiple domains for makemessages and compilemessages
commands
-+-
 Reporter:  c v t|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  2.2
  Internationalization   |
 Severity:  Normal   |   Resolution:
 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 Claude Paroz):

 Apparently this was abandoned as per
 https://code.djangoproject.com/ticket/17181#comment:9. It may be that the
 current code allows an easier implementation. We would have to see a patch
 to judge that. Do you plan to provide 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/068.a572ef49e72ebbdc91be85c833f2a2dc%40djangoproject.com.

[Django] #30721: Implicit related objects filtration because of the set Manager.

[Django]

#30721: Implicit related objects filtration because of the set Manager.
-+
   Reporter:  ApaDoctor  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  2.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 abstract model is defined with `objects` manager.
 And its child-model defines another manager - RelatedManager uses defined
 manager instead of objects.

 {{{#!python
 class SomeAbstractModel(models.Model):
 class Meta:
 abstract = True

 objects = models.Manager()


 class CustomManager(models.Manager):
 def get_queryset(self):
 return super().get_queryset().filter(some_field=True)


 class SomeThing(SomeAbstractModel):
 some_field = models.BooleanField()

 parent = models.ForeignKey(
 "SomeThing", related_name="children", on_delete=models.SET_NULL,
 null=True
 )

 custom_objects = CustomManager()
 }}}

 So we have abstract model, which defines `objects` manager for the model.

 Our model uses that abstract class.

 I created some objects:
 {{{#!python
 SomeThing(some_field=True).save()
 SomeThing.objects.bulk_create([SomeThing(some_field=bool(x%2),
 parent_id=1) for x in range(0,6)])
 }}}

 After i reloaded shell i tried to make queries:
 {{{#!python
 >>> x = SomeThing.objects.get(id=1)
 >>> x.children.count()
 3
 >>>SomeThing.objects.filter(parent_id=1).count()
 6
 }}}

 Generated raw SQL for first query is:

 {{{#!sql
 SELECT COUNT(*) AS "__count" FROM "sapp_something" WHERE
 ("sapp_something"."some_field" = true AND "some_something"."parent_id" =
 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/052.79589af8490c3aeab7c3052e2f7e39b5%40djangoproject.com.

[Django] #30720: allow specifying multiple domains for makemessages and compilemessages commands

[Django]

#30720: allow specifying multiple domains for makemessages and compilemessages
commands
+
   Reporter:  c v t |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Internationalization  |Version:  2.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 (The left-over part of #17181..)

 Currently, to update / compile catalogues for both `django` and `djangojs`
 domains, you need to run `makemessages` and `compilemessages` twice:

  django-admin.py makemessages -d django
  django-admin.py makemessages -d djangojs

 It would be lovely to be able to run this in one command, either:

  django-admin.py makemessages -d django,djangojs

 or:

  django-admin.py makemessages -d django -d djangojs

 (Currently, the first version gives an error; the second version silently
 ignores the first `-d` option, in this example it would just regenerate
 `djangojs`)

-- 
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/053.132b8653fb759a26cc2ac49d703199d9%40djangoproject.com.

Re: [Django] #21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations.

[Django]

#21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations.
-+-
 Reporter:  FunkyBob |Owner:  Dan Tao
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"85ac838d9e6975130b5c55299e9d7d1222a8e289" 85ac838d]:
 {{{
 #!CommitTicketReference repository=""
 revision="85ac838d9e6975130b5c55299e9d7d1222a8e289"
 Fixed #21039 -- Added AddIndexConcurrently/RemoveIndexConcurrently
 operations for PostgreSQL.

 Thanks to Simon Charettes for review.

 Co-Authored-By: Daniel Tao 
 }}}

-- 
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/066.8e74a8f1cd5f03b3b46de2270fd37ec2%40djangoproject.com.

Re: [Django] #21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations. (was: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations)

[Django]

#21039: Support Postgres "CREATE INDEX CONCURRENTLY" in migrations.
-+-
 Reporter:  FunkyBob |Owner:  Dan Tao
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 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 felixxm):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * component:  Migrations => contrib.postgres


-- 
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/066.2b94228734f106497ca75c59e3149fec%40djangoproject.com.

Re: [Django] #27339: Adding an AutoField prompts for a default which creates a broken migration

[Django]

#27339: Adding an AutoField prompts for a default which creates a broken 
migration
--+
 Reporter:  Tim Graham|Owner:  za
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  Version:  master
 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 za):

 * status:  new => assigned
 * owner:  nobody => za


Comment:

 I am facing the same issue, but on my case I don't have data on the
 existing table. I'll think how to solve this 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/067.6b547258a33fc216f761bfe870cb9eed%40djangoproject.com.

Re: [Django] #28107: Can't perform annotation on related table when un-managed model is backed by a DB view

[Django]

#28107: Can't perform annotation on related table when un-managed model is 
backed
by a DB view
-+-
 Reporter:  powderflask  |Owner:  Vojtěch
 |  Boček
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_docs:  0 => 1
 * stage:  Ready for checkin => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.268745e288ec1f27e96adf7f6b21ceb9%40djangoproject.com.

Re: [Django] #29391: Postgres array lookups need to call get_db_prep_value to adapt values to their db representation (FieldGetDbPrepValueMixin)

[Django]

#29391: Postgres array lookups need to call get_db_prep_value to adapt values to
their db representation (FieldGetDbPrepValueMixin)
-+-
 Reporter:  Gavin Wahl   |Owner:  vinay
 |  karanam
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  2.0
 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 felixxm):

 3.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.27b51d274fb5c43646a9c1570b1bef8a%40djangoproject.com.

Re: [Django] #29391: Postgres array lookups need to call get_db_prep_value to adapt values to their db representation (FieldGetDbPrepValueMixin)

[Django]

#29391: Postgres array lookups need to call get_db_prep_value to adapt values to
their db representation (FieldGetDbPrepValueMixin)
-+-
 Reporter:  Gavin Wahl   |Owner:  vinay
 |  karanam
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  2.0
 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 Andrey Torsunov):

 Which version of Django will have these changes? Thanks

-- 
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.eef8634531ebf206acd490c63e387162%40djangoproject.com.

Re: [Django] #29338: Can't use OuterRef in union Subquery

[Django]

#29338: Can't use OuterRef in union Subquery
-+-
 Reporter:  Matthew Pava |Owner:  (none)
 Type:  Bug  |   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
-+-

Comment (by felixxm):

 [https://github.com/django/django/pull/11692 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.f57b5394d57260624836ccf1d66ceab9%40djangoproject.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:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by felixxm):

 Javier, patch is welcome. Leaving comments doesn't change anything and is
 not helpful.

-- 
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.0b7835c820144b4f97c127317377d54e%40djangoproject.com.