Re: [Django] #15049: Using annotation before and after filter gives wrong results

#15049: Using annotation before and after filter gives wrong results -+- Reporter: Alex Gaynor |Owner: Abhinav | Yadav Type: Bug

Re: [Django] #29843: Create permissions using migration operations rather than using the post_migrate signal

#29843: Create permissions using migration operations rather than using the post_migrate signal -+- Reporter: Petter Strandmark|Owner: Arthur Type: | Rio Cleanup/

Re: [Django] #35050: Issue filtering on FilteredRelation with F object

#35050: Issue filtering on FilteredRelation with F object -+- Reporter: mrzorn |Owner: nobody Type: Bug | Status: new Component: Databa

Re: [Django] #35050: Issue filtering on FilteredRelation with F object

#35050: Issue filtering on FilteredRelation with F object --+-- Reporter: mrzorn|Owner: nobody Type: Bug | Status: new Component: Uncategorized

Re: [Django] #35050: Issue filtering on FilteredRelation with F object

#35050: Issue filtering on FilteredRelation with F object --+-- Reporter: mrzorn|Owner: nobody Type: Bug | Status: new Component: Uncategorized

[Django] #35050: Issue filtering on FilteredRelation with F object

#35050: Issue filtering on FilteredRelation with F object -+- Reporter: Mark Zorn | Owner: nobody Type: Bug| Status: new Component: |

Re: [Django] #34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True

#34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True -+- Reporter: Alain Delplanque |Owner: HAMA | Barhamou Type: New featu

Re: [Django] #35028: psycopg3: distinct query iteration causes psycopg.errors.InvalidColumnReference: for SELECT DISTINCT, ORDER BY expressions must appear in select list

#35028: psycopg3: distinct query iteration causes psycopg.errors.InvalidColumnReference: for SELECT DISTINCT, ORDER BY expressions must appear in select list -+- Reporter: Richard Ebeling |Owner:

Re: [Django] #35049: Drop support for GDAL 2.4

#35049: Drop support for GDAL 2.4 --+ Reporter: David Smith |Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

Re: [Django] #34566: ModelAdmin get_field_queryset uses related admin ordering, but not related admin querysets.

#34566: ModelAdmin get_field_queryset uses related admin ordering, but not related admin querysets. ---+--- Reporter: Mike J |Owner: Krishna2864 Type: Bug| Sta

Re: [Django] #35048: Drop support for Proj 5.x

#35048: Drop support for Proj 5.x --+ Reporter: David Smith |Owner: nobody Type: Cleanup/optimization | Status: new Component: GIS |

[Django] #35049: Drop support for GDAL 2.4

#35049: Drop support for GDAL 2.4 -+ Reporter: David Smith| Owner: nobody Type: Uncategorized | Status: new Component: GIS|Version: 5.0

[Django] #35048: Drop support for Proj 5.x

#35048: Drop support for Proj 5.x -+ Reporter: David Smith| Owner: nobody Type: Uncategorized | Status: new Component: GIS|Version: 4.2

Re: [Django] #35030: Make django.contrib.auth decorators work with async functions.

#35030: Make django.contrib.auth decorators work with async functions. --+ Reporter: Mike Lissner |Owner: Dingning Type: New feature | Status: assigned Componen

Re: [Django] #35030: Make django.contrib.auth decorators work with async functions.

#35030: Make django.contrib.auth decorators work with async functions. --+ Reporter: Mike Lissner |Owner: Dingning Type: New feature | Status: assigned Componen

Re: [Django] #35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong HTTP method

#35013: LogoutView from django.contrib.auth in Django 5.0 seems to use the wrong HTTP method ---+-- Reporter: dg |Owner: nobody Type: Bug| Status: closed

Re: [Django] #35030: Make django.contrib.auth decorators work with async functions.

#35030: Make django.contrib.auth decorators work with async functions. --+ Reporter: Mike Lissner |Owner: Dingning Type: New feature | Status: assigned Componen

Re: [Django] #35047: Wrong sql query for migration

#35047: Wrong sql query for migration +-- Reporter: mgoldenbe |Owner: nobody Type: Bug | Status: closed Component: Migrations | Version: 3.2

Re: [Django] #35047: Wrong sql query for migration

#35047: Wrong sql query for migration +-- Reporter: mgoldenbe |Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 3.2 Se

Re: [Django] #35047: Wrong sql query for migration

#35047: Wrong sql query for migration +-- Reporter: mgoldenbe |Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 3.2 Se

[Django] #35047: Wrong sql query for migration

#35047: Wrong sql query for migration --+ Reporter: mgoldenbe | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 3.2

Re: [Django] #34411: Update obsolete GDAL API for DataSource handling

#34411: Update obsolete GDAL API for DataSource handling -+- Reporter: Claude Paroz |Owner: Claude Type: | Paroz Cleanup/optimization |

Re: [Django] #34411: Update obsolete GDAL API for DataSource handling

#34411: Update obsolete GDAL API for DataSource handling -+- Reporter: Claude Paroz |Owner: Claude Type: | Paroz Cleanup/optimization |

Re: [Django] #35046: BlankChoiceIterator causes AttributeError for some existing packages and projects

#35046: BlankChoiceIterator causes AttributeError for some existing packages and projects -+-- Reporter: Hazho Human |Owner: nobody Type: Bug | Status: closed Compon