Re: [Django] #34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in

#34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in --+-- Reporter: Steven Mapes |Owner: nobody Type: Bug | Status: new

Re: [Django] #28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null

#28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null -+- Reporter: Matteo Pietro Russo |Owner: nobody Type: | Status: closed

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: new Component: Core

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: new Component: Core

Re: [Django] #34086: Confirm support for PostGIS 3.3

#34086: Confirm support for PostGIS 3.3 -+- Reporter: Paolo Melchiorre |Owner: Paolo | Melchiorre Type: New feature |

Re: [Django] #34086: Confirm support for PostGIS 3.3

#34086: Confirm support for PostGIS 3.3 -+- Reporter: Paolo Melchiorre |Owner: Paolo | Melchiorre Type: New feature |

Re: [Django] #34086: Confirm support for PostGIS 3.3

#34086: Confirm support for PostGIS 3.3 -+- Reporter: Paolo Melchiorre |Owner: Paolo | Melchiorre Type: New feature |

Re: [Django] #34086: Confirm support for PostGIS 3.3

#34086: Confirm support for PostGIS 3.3 -+- Reporter: Paolo Melchiorre |Owner: Paolo | Melchiorre Type: New feature |

[Django] #34086: Confirm support for PostGIS 3.3

#34086: Confirm support for PostGIS 3.3 -+- Reporter: Paolo | Owner: Paolo Melchiorre Melchiorre | Type: New| Status: assigned

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: new Component: Core

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: closed Component: Core

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: closed Component: Core

Re: [Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff Triplett|Owner: nobody Type: Bug | Status: new Component: Core

[Django] #34085: Black shouldn't format non-Python files

#34085: Black shouldn't format non-Python files -+- Reporter: Jeff | Owner: nobody Triplett | Type: Bug| Status: new

Re: [Django] #34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in

#34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in --+-- Reporter: Steven Mapes |Owner: nobody Type: Bug | Status: new

[Django] #34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in

#34084: Regression in Django 4.1 so ModelForms always set self.instance even when none passed in -+- Reporter: Steven | Owner: nobody Mapes |

Re: [Django] #28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null

#28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null -+- Reporter: Matteo Pietro Russo |Owner: nobody Type: | Status: closed

Re: [Django] #33735: Add asynchronous responses for use with an ASGI server

#33735: Add asynchronous responses for use with an ASGI server +-- Reporter: florianvazelle |Owner: florianvazelle Type: New feature | Status: assigned

Re: [Django] #34079: Excessive parentheses when generating a query

#34079: Excessive parentheses when generating a query ---+--- Reporter: Lelikov|Owner: Aman Pandey Type: Bug| Status: assigned Component: Uncategorized

Re: [Django] #34079: Excessive parentheses when generating a query

#34079: Excessive parentheses when generating a query ---+-- Reporter: Lelikov|Owner: nobody Type: Bug| Status: new Component: Uncategorized |

Re: [Django] #33537: Cloning test databases should reraise errors on MySQL. (was: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server)

#33537: Cloning test databases should reraise errors on MySQL. -+- Reporter: Stephen Finucane |Owner: nobody Type: | Status: new

Re: [Django] #33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server

#33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug |

Re: [Django] #33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server

#33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug |

Re: [Django] #33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server

#33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug |

Re: [Django] #33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server

#33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug |

Re: [Django] #33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server

#33537: Cloning test database fails with mysql-client 8.x and older mysql-server or mariadb-server -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug |

Re: [Django] #10088: for_share() as well as for_update() addition to Model.QuerySet

#10088: for_share() as well as for_update() addition to Model.QuerySet -+- Reporter: epandurski |Owner: xyd Type: New feature | Status: assigned

Re: [Django] #34083: Cloning test database fails with mariadb-server 8.x

#34083: Cloning test database fails with mariadb-server 8.x -+- Reporter: Stephen Finucane |Owner: nobody Type: Bug | Status: closed Component:

[Django] #34083: Cloning test database fails with mariadb-server 8.x

#34083: Cloning test database fails with mariadb-server 8.x -+- Reporter: Stephen| Owner: nobody Finucane | Type: Bug| Status: new

Re: [Django] #34059: Validation of check constraints on JSONField key transforms with None produces invalid SQL on PostgreSQL.

#34059: Validation of check constraints on JSONField key transforms with None produces invalid SQL on PostgreSQL. -+- Reporter: Dan LaManna |Owner: David

Re: [Django] #33952: Too aggressive pk control in create_reverse_many_to_one_manager

#33952: Too aggressive pk control in create_reverse_many_to_one_manager -+- Reporter: Claude Paroz |Owner: David | Wobrock Type: Bug

Re: [Django] #33984: Related managers cache gets stale after saving a fetched model with new PK

#33984: Related managers cache gets stale after saving a fetched model with new PK -+- Reporter: joeli|Owner: Mariusz | Felisiak Type:

Re: [Django] #33984: Related managers cache gets stale after saving a fetched model with new PK

#33984: Related managers cache gets stale after saving a fetched model with new PK -+- Reporter: joeli|Owner: Mariusz | Felisiak Type:

Re: [Django] #33984: Related managers cache gets stale after saving a fetched model with new PK

#33984: Related managers cache gets stale after saving a fetched model with new PK -+- Reporter: joeli|Owner: Mariusz | Felisiak Type:

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 |