Re: [Django] #33945: get_previous_in_order and get_next_in_order return incorrect data when objects is stored in non-default database

[Django]

#33945: get_previous_in_order and get_next_in_order return incorrect data when
objects is stored in non-default database
-+-
 Reporter:  François Granade |Owner:  Wael
 |  Ramadan
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 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 Wael Ramadan):

 * cc: Wael Ramadan (added)
 * owner:  nobody => Wael Ramadan
 * 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/01070182c40874a4-9f05d5af-3996-4503-8782-7506afeb2aaf-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

[Django]

#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+-
 Reporter:  damoncheng|Owner:  damoncheng
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 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
--+-
Changes (by JM Barbier):

 * cc: JM Barbier (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/01070182c3284a91-d694d67e-3ab4-4d49-970a-d2d9662b71b7-00%40eu-central-1.amazonses.com.

Re: [Django] #33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is not set.

[Django]

#33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is
not set.
-+-
 Reporter:  Craig de Stigter |Owner:  Kinza-
 Type:   |  Raza
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 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 Kinza-Raza):

 * has_patch:  0 => 1


Comment:

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

-- 
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/01070182c1e91e78-24862de7-f053-4aed-a661-c6adf4910e4a-00%40eu-central-1.amazonses.com.

[Django] #33945: get_previous_in_order and get_next_in_order return incorrect data when objects is stored in non-default database

[Django]

#33945: get_previous_in_order and get_next_in_order return incorrect data when
objects is stored in non-default database
-+-
   Reporter:  François   |  Owner:  nobody
  Granade|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.0
  layer (models, ORM)|
   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  |
-+-
 Using the a simple model with an `order_with_respect_to` (slight variation
 of the models in
 https://github.com/django/django/blob/main/tests/multiple_database/models.py):

 {{{
 class Person(models.Model):
 name = models.CharField(max_length=100, unique=True)


 class Pet(models.Model):
 name = models.CharField(max_length=100)
 owner = models.ForeignKey(Person, models.CASCADE)

 class Meta:
 order_with_respect_to = "owner"

 }}}

 then adding some object, and declaring an order for the pets:

 {{{
  human = Person.objects.using("other").create(name="Human")
 dog = Pet.objects.using("other").create(name="Dog", owner=human)
 cat = Pet.objects.using("other").create(name="Cat", owner=human)
 duck = Pet.objects.using("other").create(name="Duck", owner=human)
 human.set_pet_order([duck.pk, dog.pk, cat.pk], "other")

 }}}

 Then simply trying to get the previous or next pet will fail:

 {{{
 >>> dog.get_next_in_order()  # would expect `cat`
 models.Pet.DoesNotExist: Pet matching query does not exist.
 >>> dog.get_previous_in_order()  # would expect `duck`
 models.Pet.DoesNotExist: Pet matching query does not exist.
 }}}

-- 
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/01070182c18ecd5d-f0d5641d-9e80-4cc4-aba5-bb242f0dcab7-00%40eu-central-1.amazonses.com.

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

[Django]

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  Tetsuya Morimoto |Owner:  François
 |  Granade
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by François Granade):

 * owner:  (none) => François Granade
 * 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/01070182c17c5c26-04dcf9b6-21e3-45a2-b9c5-5bfc67925362-00%40eu-central-1.amazonses.com.

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

[Django]

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
 Reporter:  Tetsuya Morimoto |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  multi-db | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by François Granade):

 Proposing a 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/01070182c17c44c9-689baf75-798e-463d-84d3-abca2614702c-00%40eu-central-1.amazonses.com.