Re: [Django] #31289: system checks: admin.E002 could provide a hint but doesn't

#31289: system checks: admin.E002 could provide a hint but doesn't -+- Reporter: Keryn Knight |Owner: Sanskar Type: | Jaiswal Cleanup/optimization

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

#31185: fields.E310-E311 should take into account UniqueConstraints without conditions. -+- Reporter: Pavel Garkin |Owner: Ahmad | Abdallah

Re: [Django] #30581: Allow constraints to be used for validation (in Python)

#30581: Allow constraints to be used for validation (in Python) -+- Reporter: Carlton Gibson |Owner: Sanskar | Jaiswal Type: New feature

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

#31185: fields.E310-E311 should take into account UniqueConstraints without conditions. -+- Reporter: Pavel Garkin |Owner: Ahmad | Abdallah

Re: [Django] #31285: Inherited model doesn't correctly order by "-pk" when specified on Parent.Meta.ordering

#31285: Inherited model doesn't correctly order by "-pk" when specified on Parent.Meta.ordering -+- Reporter: Jon Dufresne |Owner: nobody Type: Bug |

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

#28919: Add support for Common Table Expression (CTE) queries -+- Reporter: Daniel Miller|Owner: Moses | Mugisha Type: New feature |

Re: [Django] #30422: Temporary files do not get deleted on canceled upload request.

#30422: Temporary files do not get deleted on canceled upload request. -+- Reporter: drutalj |Owner: Sanskar | Jaiswal Type: Bug

Re: [Django] #31290: Unable to runserver - python manage.py runserver

#31290: Unable to runserver - python manage.py runserver ---+-- Reporter: batistalucash |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

[Django] #31290: Unable to runserver - python manage.py runserver

#31290: Unable to runserver - python manage.py runserver -+ Reporter: batistalucash | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #31289: system checks: admin.E002 could provide a hint but doesn't

#31289: system checks: admin.E002 could provide a hint but doesn't --+ Reporter: Keryn Knight |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #30040: Use a default permission name in docs examples to avoid confusion

#30040: Use a default permission name in docs examples to avoid confusion -+- Reporter: Adrian Samatan |Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #30040: Use a default permission name in docs examples to avoid confusion

#30040: Use a default permission name in docs examples to avoid confusion -+- Reporter: Adrian Samatan |Owner: Hasan Type: | Ramezani Cleanup/optimization

[Django] #31289: system checks: admin.E002 could provide a hint but doesn't

#31289: system checks: admin.E002 could provide a hint but doesn't + Reporter: Keryn Knight | Owner: nobody Type: New feature | Status: new

Re: [Django] #31287: Rename mark_safe and "safe" template filters to something less safe sounding

#31287: Rename mark_safe and "safe" template filters to something less safe sounding -+- Reporter: Adam (Chainz)|Owner: nobody Johnson| Type:

Re: [Django] #31287: Rename mark_safe and "safe" template filters to something less safe sounding

#31287: Rename mark_safe and "safe" template filters to something less safe sounding -+- Reporter: Adam (Chainz)|Owner: nobody Johnson| Type:

Re: [Django] #31224: Add asynchronous views.

#31224: Add asynchronous views. --+- Reporter: felixxm |Owner: Andrew Godwin Type: New feature | Status: assigned Component: Core (Other) |

Re: [Django] #31286: Database specific fields checks should be databases aware.

#31286: Database specific fields checks should be databases aware. -+- Reporter: Hongtao Ma |Owner: Hongtao | Ma Type: Bug |

Re: [Django] #31276: Add 'flush' option to only clear non-empty tables

#31276: Add 'flush' option to only clear non-empty tables -+- Reporter: Adam (Chainz)|Owner: jonatron Johnson| Type: |

Re: [Django] #31276: Add 'flush' option to only clear non-empty tables

#31276: Add 'flush' option to only clear non-empty tables -+- Reporter: Adam (Chainz)|Owner: jonatron Johnson| Type: |

Re: [Django] #31276: Add 'flush' option to only clear non-empty tables

#31276: Add 'flush' option to only clear non-empty tables -+- Reporter: Adam (Chainz)|Owner: jonatron Johnson| Type: |

Re: [Django] #31288: New ReplaceAuthMiddleware feature. (was: New ReplaceAuthMiddleware feature)

#31288: New ReplaceAuthMiddleware feature. -+- Reporter: Théo Huchard |Owner: Théo | Huchard Type: New feature |

Re: [Django] #31286: Database specific fields checks should be databases aware.

#31286: Database specific fields checks should be databases aware. -+- Reporter: Hongtao Ma |Owner: Hongtao | Ma Type: Bug |

Re: [Django] #30040: Use a default permission name in docs examples to avoid confusion

#30040: Use a default permission name in docs examples to avoid confusion -+- Reporter: Adrian Samatan |Owner: Hasan Type: | Ramezani Cleanup/optimization

Re: [Django] #31288: New ReplaceAuthMiddleware feature

#31288: New ReplaceAuthMiddleware feature -+- Reporter: Théo Huchard |Owner: Théo | Huchard Type: New feature |

Re: [Django] #31288: New ReplaceAuthMiddleware feature

#31288: New ReplaceAuthMiddleware feature -+- Reporter: Théo Huchard |Owner: Théo | Huchard Type: New feature |

Re: [Django] #31286: Database specific fields checks should be databases aware.

#31286: Database specific fields checks should be databases aware. -+- Reporter: Hongtao Ma |Owner: Hongtao | Ma Type: Bug |

Re: [Django] #31288: New ReplaceAuthMiddleware feature

#31288: New ReplaceAuthMiddleware feature -+- Reporter: TheoHd |Owner: nobody Type: New feature | Status: new Component: contrib.auth

[Django] #31288: New ReplaceAuthMiddleware feature

#31288: New ReplaceAuthMiddleware feature -+- Reporter: TheoHd | Owner: nobody Type: New| Status: new feature|

Re: [Django] #31286: Database specific fields checks should be databases aware.

#31286: Database specific fields checks should be databases aware. -+- Reporter: Hongtao Ma |Owner: Hongtao | Ma Type: Bug |

Re: [Django] #28699: REMOTE_USER issues with CSRF

#28699: REMOTE_USER issues with CSRF --+ Reporter: stephanm |Owner: Rodrigo Type: Bug | Status: assigned Component: contrib.auth | Version:

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

#31185: fields.E310-E311 should take into account UniqueConstraints without conditions. -+- Reporter: Pavel Garkin |Owner: Ahmad | Abdallah

Re: [Django] #31286: Database specific fields checks should be databases aware. (was: Database specific checks always goes to the 'default' backend)

#31286: Database specific fields checks should be databases aware. -+- Reporter: Hongtao Ma |Owner: nobody Type: Bug | Status: new

Re: [Django] #31185: fields.E310-E311 should take into account UniqueConstraints without conditions.

#31185: fields.E310-E311 should take into account UniqueConstraints without conditions. -+- Reporter: Pavel Garkin |Owner: Ahmad | Abdallah

Re: [Django] #31187: Detection of existing total ordering in admin changelist should take into account UniqueConstraints without conditions.

#31187: Detection of existing total ordering in admin changelist should take into account UniqueConstraints without conditions. -+- Reporter: Fabio Sangiovanni|Owner: Fabio

Re: [Django] #31187: Detection of existing total ordering in admin changelist should take into account UniqueConstraints without conditions.

#31187: Detection of existing total ordering in admin changelist should take into account UniqueConstraints without conditions. -+- Reporter: Fabio Sangiovanni|Owner: Fabio

[Django] #31287: Rename mark_safe and "safe" template filters to something less safe sounding

#31287: Rename mark_safe and "safe" template filters to something less safe sounding -+ Reporter: Adam (Chainz) Johnson | Owner: nobody Type: Cleanup/optimization |

[Django] #31286: Database specific checks always goes to the 'default' backend

#31286: Database specific checks always goes to the 'default' backend -+- Reporter: Hongtao| Owner: nobody Ma | Type: Bug|