Re: [Django] #33796: Combined queries with ordering are no longer usable as subqueries on PostgreSQL and MySQL.

[Django]

#33796: Combined queries with ordering are no longer usable as subqueries on
PostgreSQL and MySQL.
-+-
 Reporter:  Shai Berger  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15793 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/01070181943ada1a-fb0a31e1-d37b-41f4-814d-3c321c81275b-00%40eu-central-1.amazonses.com.

Re: [Django] #27505: Error messages customization and internationalization in Paginator class

[Django]

#27505: Error messages customization and internationalization in Paginator class
-+-
 Reporter:  Anton Bazhanov   |Owner:  Pedro
 Type:   |  Magno Müller
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Pedro Magno Müller):

 * owner:  (none) => Pedro Magno Müller
 * status:  new => assigned


Comment:

 Hi, I'm a new contributor and I'd love to give it a try

-- 
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/0107018191f68005-9935a6d2-bbc0-44dc-a1f2-3d3d645be458-00%40eu-central-1.amazonses.com.

Re: [Django] #33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES

[Django]

#33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak ):

 In [changeset:"b37a4affcd0e28ed9266e96c04ceadd2b3396aea" b37a4af]:
 {{{
 #!CommitTicketReference repository=""
 revision="b37a4affcd0e28ed9266e96c04ceadd2b3396aea"
 [4.1.x] Fixed #33800 -- Fixed system check for the same template tag
 module in installed apps and template tag libraries.

 Thanks Claude Paroz for the report.

 Regression in 004b4620f6f4ad87261e149898940f2dcd5757ef.
 Backport of 083bfca6b6c00d0f45837a65c2db721eaf46bc07 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/0107018191cf4d82-4ec5cffb-4158-48b2-b5f6-940f16f604c9-00%40eu-central-1.amazonses.com.

Re: [Django] #33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES

[Django]

#33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  4.1
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"083bfca6b6c00d0f45837a65c2db721eaf46bc07" 083bfca6]:
 {{{
 #!CommitTicketReference repository=""
 revision="083bfca6b6c00d0f45837a65c2db721eaf46bc07"
 Fixed #33800 -- Fixed system check for the same template tag module in
 installed apps and template tag libraries.

 Thanks Claude Paroz for the report.

 Regression in 004b4620f6f4ad87261e149898940f2dcd5757ef.
 }}}

-- 
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/0107018191ce0725-5b9f9f61-5066-4d6a-b783-8343ccdc15ba-00%40eu-central-1.amazonses.com.

Re: [Django] #33802: Q objects to match an empty string in CheckConstraint results in invalid SQL using MySQL

[Django]

#33802: Q objects to match an empty string in CheckConstraint results in invalid
SQL using MySQL
-+--
 Reporter:  Phil Gyford  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.0
 Severity:  Normal   |   Resolution:  worksforme
 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 Phil Gyford):

 Fair enough!

 Very strange. I’ve tried several variations and always had the same error,
 but I’ve only tried it with this one MariaDB-using project, and one other
 that used SQLite (that didn’t have the error).

-- 
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/0107018191c0beb7-0c4fd939-2a7c-46c3-8f87-db803da2024f-00%40eu-central-1.amazonses.com.

Re: [Django] #33802: Q objects to match an empty string in CheckConstraint results in invalid SQL using MySQL (was: Using a Q object to match an empty string in CheckConstraint results in invalid SQL

[Django]

#33802: Q objects to match an empty string in CheckConstraint results in invalid
SQL using MySQL
-+--
 Reporter:  Phil Gyford  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  4.0
 Severity:  Normal   |   Resolution:  worksforme
 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
 * type:  Uncategorized => Bug
 * resolution:   => worksforme


Comment:

 Thanks for this ticket, however it works for me with MariaDB, MySQL, and
 other built-in backends (I checked with Django 3.0, 3.1, 3.2, 4.0, 4.1,
 and on the current `main` branch)
 {{{
 --
 -- Create constraint sample_othermodel_firstname on model othermodel
 --
 ALTER TABLE `sample_othermodel` ADD CONSTRAINT
 `sample_othermodel_firstname` CHECK (`firstname` = '');
 }}}

-- 
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/010701819196df77-51d5a8e1-3768-4665-93b1-769dc7284947-00%40eu-central-1.amazonses.com.

[Django] #33803: Add crossorigin attribute to django admin templates

[Django]

#33803: Add crossorigin attribute to django admin templates
-+-
   Reporter: |  Owner:  nobody
  fcrozatier |
   Type:  Bug| Status:  new
  Component: |Version:  4.0
  contrib.admin  |
   Severity:  Normal |   Keywords:  crossorigin COEP
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When we store our static files on a cloud (digitalocean Spaces in my case)
 and we have Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy
 headers on the loadbalancer the files are blocked since they are not same-
 origin. This is usually not a problem we just have to add a crossorigin
 attribute, but in the case of django admin files the templates do not set
 them.

 Should we add the ''crossorigin'' attribute to the **script**,  **link**
 and **img** tags of the template files ?

 Without this attribute the files are blocked with Cross-Origin Opener
 Policy.

-- 
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/010701819191add9-43b51a4e-8a08-4a79-a329-1bc4f10f9928-00%40eu-central-1.amazonses.com.

[Django] #33802: Using a Q object to match an empty string in CheckConstraint results in invalid SQL using MySQL

[Django]

#33802: Using a Q object to match an empty string in CheckConstraint results in
invalid SQL using MySQL
-+
   Reporter:  Phil Gyford|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Migrations |Version:  4.0
   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  |
-+
 Using a constraint like that below results in a migration that generates
 invalid SQL when using a MariaDB (v10.3) database. I think it's OK using
 SQLite, but I haven't tried Postgresql.

 {{{
 from django.db import models
 from django.db.models import Q

 class Person(models.Model):
 firstname = models.CharField(max_length=50, blank=True, null=False,
 default="")

 class Meta:
 constraints = [
 models.CheckConstraint(
 name="%(app_label)s_%(class)s_firstname",
 check=(Q(firstname__exact="")),
 )
 ]
 }}}

 Running `manage.py makemigrations` results in a migration with this
 operation:

 {{{
 constraint=models.CheckConstraint(
 check=models.Q(("firstname__exact", "")),
 name="myapp_person_firstname",
 ),
 }}}

 And running `manage.py sqlmigrate myapp 0002` shows this (note there
 should be a pair of empty quotes between `=` and `)` at the end):

 {{{
 ALTER TABLE `Person` ADD CONSTRAINT `myapp_person_firstname` CHECK
 (`firstname` = );
 }}}

 Unsurprisingly, running the migration results in:

 {{{
 django.db.utils.ProgrammingError: (1064, "1064 (42000): You have an error
 in your SQL syntax; check the manual that corresponds to your MariaDB
 server version for the right syntax to use near ')' at line 1", '42000')
 }}}

-- 
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/010701819107b1ac-15afe151-484c-4f72-bbd4-8b82e1e4d7d6-00%40eu-central-1.amazonses.com.

Re: [Django] #33801: IsNull Lookup requesting a attribute from RHS while it is force to be of type bool

[Django]

#33801: IsNull Lookup requesting a attribute from RHS while it is force to be of
type bool
-+-
 Reporter:  Bart Kalkman |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  Lookup, IsNull,  | Triage Stage:
  Models |  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


Comment:

 Duplicate of #33705, fixed in Django 4.0.5 (see
 9f5548952906c6ea97200c016734b4f519520a64).

-- 
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/0107018190c5002e-6dc7752b-d7b1-4b85-ad30-9ad022de4069-00%40eu-central-1.amazonses.com.

[Django] #33801: IsNull Lookup requesting a attribute from RHS while it is force to be of type bool

[Django]

#33801: IsNull Lookup requesting a attribute from RHS while it is force to be of
type bool
-+-
   Reporter: |  Owner:  nobody
  BartKalkman|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.0
  layer (models, ORM)|   Keywords:  Lookup, IsNull,
   Severity:  Normal |  Models
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When using the {{{ django.db.models.lookups.IsNull }}} directly it forces
 you to use a bool for the RHS, else you will get an error saying to use
 True of False.
 When using True or False you will get an error saying {{{ AttributeError:
 'bool' object has no attribute 'resolve_expression' }}}

-- 
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/0107018190ac9a27-672fd959-e1d8-4084-b1e2-11f16b090759-00%40eu-central-1.amazonses.com.

Re: [Django] #33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES

[Django]

#33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  4.1
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/15790 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/01070181903a47d9-28c7cf56-804c-4ea0-b218-6cb9f40ef88a-00%40eu-central-1.amazonses.com.

Re: [Django] #33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES

[Django]

#33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  4.1
 Severity:  Release blocker  |   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):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned
 * component:  Uncategorized => Template system
 * severity:  Normal => Release blocker


Comment:

 Thanks for the report. It's a bug in the new system check (see
 004b4620f6f4ad87261e149898940f2dcd5757ef and #32987).

-- 
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/010701819036867a-dd6f55e1-c393-47e6-9341-37c3f1e5424c-00%40eu-central-1.amazonses.com.

[Django] #33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES

[Django]

#33800: check_for_template_tags_with_the_same_name with libraries in TEMPLATES
-+
   Reporter:  Claude Paroz   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  4.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  |
-+
 I didn't explore this thoroughly, but I think there might be an issue with
 the `check_for_template_tags_with_the_same_name` when you add a template
 tag library into `TEMPLATES['OPTIONS']['librairies']`.

 I'm getting an error like:
 (templates.E003) 'my_tags' is used for multiple template tag modules:
 'someapp.templatetags.my_tags', 'someapp.templatetags.my_tags'

-- 
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/0107018190182232-2b77d44f-4652-44cd-9ed7-bee5c4f6e4f4-00%40eu-central-1.amazonses.com.

Re: [Django] #31685: Support updating conflicts with QuerySet.bulk_create().

[Django]

#31685: Support updating conflicts with QuerySet.bulk_create().
-+-
 Reporter:  Vitor Pereira|Owner:  Chih Sean
 |  Hsu
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  bulk insert update   | Triage Stage:  Ready for
  upsert |  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:"531c96de34d746a58b9b7320378296730312c016" 531c96de]:
 {{{
 #!CommitTicketReference repository=""
 revision="531c96de34d746a58b9b7320378296730312c016"
 [4.1.x] Fixed #33799, Refs #31685 -- Added parameters for updating
 conflicts to QuerySeta.abulk_create().

 Backport of c627226d05dd52aef59447dcfb29cec2c2b11b8a 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/010701819010c414-c4df7f48-2c9b-41ad-85a8-08eadd194b95-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create() doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create() doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  async orm| 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:"531c96de34d746a58b9b7320378296730312c016" 531c96de]:
 {{{
 #!CommitTicketReference repository=""
 revision="531c96de34d746a58b9b7320378296730312c016"
 [4.1.x] Fixed #33799, Refs #31685 -- Added parameters for updating
 conflicts to QuerySeta.abulk_create().

 Backport of c627226d05dd52aef59447dcfb29cec2c2b11b8a 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/010701819010c439-99f31aa3-8816-4cad-9e33-775dd62e09ae-00%40eu-central-1.amazonses.com.

Re: [Django] #31685: Support updating conflicts with QuerySet.bulk_create().

[Django]

#31685: Support updating conflicts with QuerySet.bulk_create().
-+-
 Reporter:  Vitor Pereira|Owner:  Chih Sean
 |  Hsu
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  bulk insert update   | Triage Stage:  Ready for
  upsert |  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:"c627226d05dd52aef59447dcfb29cec2c2b11b8a" c627226d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c627226d05dd52aef59447dcfb29cec2c2b11b8a"
 Fixed #33799, Refs #31685 -- Added parameters for updating conflicts to
 QuerySeta.abulk_create().
 }}}

-- 
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/0107018190105648-15ffdda6-7a2a-46a6-ae24-80e1dfe8cac4-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create() doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create() doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  async orm| 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:"c627226d05dd52aef59447dcfb29cec2c2b11b8a" c627226d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c627226d05dd52aef59447dcfb29cec2c2b11b8a"
 Fixed #33799, Refs #31685 -- Added parameters for updating conflicts to
 QuerySeta.abulk_create().
 }}}

-- 
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/0107018190105674-81b78779-5837-437e-8139-fe9f9ce25f04-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  dev
 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 Mariusz Felisiak):

 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 [https://github.com/django/django/pull/15789 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/010701818fd37e7a-94008059-3351-42a8-ba07-9c12481fdf63-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  dev
 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 Hrushikesh Vaidya):

 [https://github.com/django/django/pull/15789 PR]
 I'll also add docs for `json_script()` soon

-- 
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/010701818fcf96b3-0a4d50bb-b473-47a6-9ea1-3931a0caaa39-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  dev
 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 Hrushikesh Vaidya):

 * owner:  nobody => Hrushikesh Vaidya
 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701818fb6506e-47be092a-f329-4376-b7e2-013069afef8b-00%40eu-central-1.amazonses.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:  dev
  (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 Brian Helba):

 * cc: Brian Helba (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/010701818faf2b24-c9dc27b6-3fc2-4499-b9e8-49af11b075a7-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create() doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create() doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  async orm| 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 Dhruva Patil):

 Replying to [comment:2 Mariusz Felisiak]:
 > Thanks for the report.

 No worries!

 I've raised a PR for the same: https://github.com/django/django/pull/15788

 Let me know if any changes are required.

-- 
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/010701818f7e483f-ee76b277-47f3-44a8-befa-98496822bc7b-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create() doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create() doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  async orm| 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/010701818f7d6041-0b02bb07-7a6c-460c-be74-a24737944653-00%40eu-central-1.amazonses.com.

Re: [Django] #33770: Add bulk_update() support for unique fields instead of only primary key

[Django]

#33770: Add bulk_update() support for unique fields instead of only primary key
-+-
 Reporter:  Ebram Shehata|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  models, orm  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hi Ebram.

 Yes, I'm following the thread there.

 Jerch's reply seems positive: "Overall this sounds like a valuable API
 addition to bulk_update…" but he raises the complexity of the MTI case,
 and also whether it's needed:

 > NB: Btw fetching proper pks upfront from some other unique field is
 > typically very cheap compared to bulk_update runtime itself, given you
 > have indexed those columns.

 Short of further input, if you're keen to keep working on this, I'd
 suggest adding some tests for the MTI case, and making that work. From
 there — assuming it's not too complex -- you have a decent case for a
 quality of life 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/010701818f6f1cbe-9098afcc-5d39-44cb-8460-b32ba2435b56-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create() doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields) (was: abulk_create doesn't accept upsert parameters (update_conflicts, update_fiel

[Django]

#33799: abulk_create() doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  async orm| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * type:  Uncategorized => Bug
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report.

-- 
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/010701818f662cc2-22c86409-0916-48de-a2cc-295df79e77bc-00%40eu-central-1.amazonses.com.

Re: [Django] #33799: abulk_create doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
 Reporter:  Dhruva Patil |Owner:  Dhruva
 |  Patil
 Type:  Uncategorized|   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  async orm| Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dhruva Patil):

 * 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/010701818f63b0c4-01e3b1df-769d-44ff-8187-25da7f220539-00%40eu-central-1.amazonses.com.

[Django] #33799: abulk_create doesn't accept upsert parameters (update_conflicts, update_fields, unique_fields)

[Django]

#33799: abulk_create doesn't accept upsert parameters (update_conflicts,
update_fields, unique_fields)
-+-
   Reporter:  Dhruva |  Owner:  Dhruva Patil
  Patil  |
   Type: | Status:  assigned
  Uncategorized  |
  Component:  Database   |Version:  4.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  async orm
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 abulk_create doesn't accept newly added upsert parameters even though the
 (preview) docs say it does.

 {{{
 File /usr/local/lib/python3.8/site-
 packages/django/db/models/manager.py:85, in
 
BaseManager._get_queryset_methods..create_method..manager_method(self,
 *args, **kwargs)
  84 def manager_method(self, *args, **kwargs):
 ---> 85 return getattr(self.get_queryset(), name)(*args, **kwargs)

 TypeError: abulk_create() got an unexpected keyword argument
 'update_conflicts'
 }}}

-- 
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/010701818f55ec39-02d30687-5b17-4180-b657-1124e6560be9-00%40eu-central-1.amazonses.com.

Re: [Django] #27704: contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class

[Django]

#27704: contrib.postgres.ArrayField with choices should use
TypedMultipleChoiceField as its default form field class
-+-
 Reporter:  Carl Meyer   |Owner:  Anvesh
 |  Mishra
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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 Anvesh Mishra):

 * owner:  (none) => Anvesh Mishra
 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701818f2b2736-418dd2e9-5aee-4ffe-bd09-59f02038a077-00%40eu-central-1.amazonses.com.