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

#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

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

#29748: Add AUTH_GROUP_MODEL setting to swap the group model --+- Reporter: damoncheng|Owner: damoncheng Type: New feature | Status: assigned Component:

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

#33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is not set. -+- Reporter: Craig de Stigter |Owner: Kinza- Type: | Raza

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

#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|

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

#15130: Model.validate_unique method doesn't take in account multi-db -+- Reporter: Tetsuya Morimoto |Owner: François | Granade Type: Bug

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

#15130: Model.validate_unique method doesn't take in account multi-db -+- Reporter: Tetsuya Morimoto |Owner: (none) Type: Bug | Status: new