Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Uncategorized| Status: new Component: Database laye

[Django] #30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid

#30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid -+- Reporter: thoha | Owner: nobody Type: Bug

Re: [Django] #30000: QuerySet constructed with .union() should raise an exception on unsupported filter() attempt.

#3: QuerySet constructed with .union() should raise an exception on unsupported filter() attempt. -+- Reporter: thoha|Owner: Hasan | Ramezani

Re: [Django] #30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid

#30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid -+- Reporter: thoha|Owner: nobody Type: Bug

Re: [Django] #29027: file_move_safe error with SELinux

#29027: file_move_safe error with SELinux -+- Reporter: bhargu |Owner: nobody Type: Bug | Status: new Component: File |

Re: [Django] #30010: Add support for running the test suite through docker with docker-compose

#30010: Add support for running the test suite through docker with docker-compose ---+ Reporter: Tom Forbes |Owner: nobody Type: New feature| Status: new

Re: [Django] #29027: file_move_safe() PermissionError with SELinux (was: file_move_safe error with SELinux)

#29027: file_move_safe() PermissionError with SELinux --+ Reporter: bhargu|Owner: nobody Type: Bug | Status: new Component: File upl

Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Bug | Status: new Component: Database laye

[Django] #30015: HTTP server doesn't clear previous request data in keep-alive connection.

#30015: HTTP server doesn't clear previous request data in keep-alive connection. -+- Reporter: kalekseev | Owner: nobody Type: | Status: new Uncategorized

Re: [Django] #28699: Document middleware ordering requirements following CSRF change in Django 1.11.6

#28699: Document middleware ordering requirements following CSRF change in Django 1.11.6 ---+ Reporter: stephanm |Owner: Rodrigo Type: Bug| Status: assigned

[Django] #30016: Test regressions with sqlite3 3.26.0 (vs 3.25.3)

#30016: Test regressions with sqlite3 3.26.0 (vs 3.25.3) -+- Reporter: Chris | Owner: nobody Lamb | Type: Bug| Status: new

Re: [Django] #28699: Document middleware ordering requirements following CSRF change in Django 1.11.6

#28699: Document middleware ordering requirements following CSRF change in Django 1.11.6 ---+ Reporter: stephanm |Owner: Rodrigo Type: Bug| Status: assigned

Re: [Django] #30015: HTTP server doesn't clear previous request data in keep-alive connection.

#30015: HTTP server doesn't clear previous request data in keep-alive connection. + Reporter: kalekseev |Owner: nobody Type: Bug | Status: new

Re: [Django] #30016: Test regressions with sqlite3 3.26.0 (vs 3.25.3)

#30016: Test regressions with sqlite3 3.26.0 (vs 3.25.3) -+- Reporter: Chris Lamb |Owner: nobody Type: Bug | Status: closed Component: Data

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema (was: SQLite database migration breaks ForeignKey constraint, leaving

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #30009: Invalid SQL query when using Subquery, caused by table alias quoting.

#30009: Invalid SQL query when using Subquery, caused by table alias quoting. -+- Reporter: Davit Mikava |Owner: nobody Type: Bug | Status: new

Re: [Django] #30009: Invalid SQL query when using Subquery, caused by table alias quoting.

#30009: Invalid SQL query when using Subquery, caused by table alias quoting. -+- Reporter: Davit Mikava |Owner: nobody Type: Bug | Status: new

Re: [Django] #30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid

#30014: Initialising disabled ModelChoiceField yields 'Select a valid choice'-error despite initialised option being valid -+- Reporter: thoha|Owner: nobody Type: Bug

Re: [Django] #30003: Manage.py entry point

#30003: Manage.py entry point -+- Reporter: James Pic|Owner: nobody Type: | Status: closed Cleanup/optimization | Comp

Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Bug | Status: new Component: Database laye

Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Bug | Status: new Component: Database laye

Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Bug | Status: new Component: Database laye

[Django] #30017: Django should assume port 443 for https in django.utils.http.is_same_domain()

#30017: Django should assume port 443 for https in django.utils.http.is_same_domain() -+ Reporter: Tagar | Owner: nobody Type: Bug| Status: new C

Re: [Django] #30005: Example in documentation of transaction.atomic uses both decorator and context manager

#30005: Example in documentation of transaction.atomic uses both decorator and context manager ---+-- Reporter: Peter Hull |Owner: Peter Hull Type: Bug| Status: cl

Re: [Django] #30011: Count with filter annotation bug on filter

#30011: Count with filter annotation bug on filter -+- Reporter: Taqi Abbas |Owner: nobody Type: Bug | Status: closed Component: Database l

Re: [Django] #29986: ngettext_lazy result doesn't support `.format`

#29986: ngettext_lazy result doesn't support `.format` -+- Reporter: patrick |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #29932: QuerySet.difference() after intersection() returns incorrect results on SQLite and Oracle

#29932: QuerySet.difference() after intersection() returns incorrect results on SQLite and Oracle -+- Reporter: michaeldel |Owner: felixxm Type: Bug |

Re: [Django] #30009: Invalid SQL query when using Subquery, caused by table alias quoting.

#30009: Invalid SQL query when using Subquery, caused by table alias quoting. -+- Reporter: Davit Mikava |Owner: nobody Type: Bug | Status: closed

Re: [Django] #30009: Invalid SQL query when using Subquery, caused by table alias quoting.

#30009: Invalid SQL query when using Subquery, caused by table alias quoting. -+- Reporter: Davit Mikava |Owner: nobody Type: Bug | Status: new

Re: [Django] #29214: Invalid SQL generated when annotating a subquery with an outerref to an annotated field. (was: Invalid SQL when updating after annotating using subquery)

#29214: Invalid SQL generated when annotating a subquery with an outerref to an annotated field. -+- Reporter: Oskar Persson|Owner: nobody Type: Bug |

Re: [Django] #29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion of atomic DDL.

#29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion of atomic DDL. --+ Reporter: Nathan Klug |Owner: Rodrigo Type: Cleanup/optimization |

Re: [Django] #29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion of atomic DDL.

#29895: Adjust atomic DDL documentation to avoid ambiguity with MySQL 8+ notion of atomic DDL. --+ Reporter: Nathan Klug |Owner: Rodrigo Type: Cleanup/optimization |

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #28766: Add route information to ResolverMatch

#28766: Add route information to ResolverMatch -+- Reporter: Benjamin Wohlwend|Owner: Melvyn | Sopacua Type: New feature |

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status:

Re: [Django] #29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema

#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving __old in db schema --+ Reporter: ezaquarii |Owner: nobody Type: Bug | Status: