Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: Akash | Kumar Sen Type: Bug |

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #30355: Specifying custom manager doesn't work with prefetch

#30355: Specifying custom manager doesn't work with prefetch ---+--- Reporter: Kyle Mulka |Owner: Akash Kumar Sen Type: Bug| Status: assigned Component:

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: Akash | Kumar Sen Type: Bug |

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34637: Add support for database defaults in questioner.

#34637: Add support for database defaults in questioner. -+-- Reporter: Bhuvnesh |Owner: Bhuvnesh Type: New feature | Status: closed Component: Migrations |

Re: [Django] #34609: Deprecate format_html calls without args or kwargs

#34609: Deprecate format_html calls without args or kwargs -+- Reporter: Adam Johnson |Owner: Bhuvnesh Type: | Status: closed

Re: [Django] #34532: Form.default_renderer is ignored in formsets.

#34532: Form.default_renderer is ignored in formsets. -+- Reporter: Ryan Burt|Owner: | Christopher Cave-Ayland Type: Bug |

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

#32210: Django Admin with Inlines not using UUIDField default value --+ Reporter: Joseph Metzinger |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+ Reporter: Andrei Shabanski |Owner: Neeraj Kumar Type: Bug | Status: assigned

Re: [Django] #34630: Neither `pgettext` nor `pgettext_lazy` return contextual markers in PO files

#34630: Neither `pgettext` nor `pgettext_lazy` return contextual markers in PO files -+- Reporter: Kamil Paduszyński|Owner: nobody Type: Bug | Status:

Re: [Django] #34636: Add documentation for Query's function `sql_with_params`

#34636: Add documentation for Query's function `sql_with_params` -+- Reporter: Paolo Melchiorre |Owner: nobody Type: New feature | Status: closed

Re: [Django] #34631: Expression.identity() performance

#34631: Expression.identity() performance -+- Reporter: Blaž Šnuderl |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #26803: Add a statistics option to makemessages

#26803: Add a statistics option to makemessages --+ Reporter: Vlastimil Zíma|Owner: (none) Type: New feature | Status: new Component:

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+-- Reporter: Andrei Shabanski |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable --+-- Reporter: Andrei Shabanski |Owner: nobody Type: Bug | Status: new Component:

[Django] #34638: Rows are selected if BooleanField is in list_editable

#34638: Rows are selected if BooleanField is in list_editable + Reporter: Andrei Shabanski | Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: Akash | Kumar Sen Type: Bug |

Re: [Django] #34637: Add support for database defaults in questioner.

#34637: Add support for database defaults in questioner. -+- Reporter: Bhuvnesh |Owner: Bhuvnesh Type: New feature | Status: assigned Component:

Re: [Django] #34637: Add support for database defaults in questioner.

#34637: Add support for database defaults in questioner. -+- Reporter: Bhuvnesh |Owner: nobody Type: New feature | Status: assigned Component:

[Django] #34637: Add support for database defaults in questioner.

#34637: Add support for database defaults in questioner. -+- Reporter: Bhuvnesh | Owner: nobody Type: New| Status: assigned feature

[Django] #34636: Add documentation for Query's function `sql_with_params`

#34636: Add documentation for Query's function `sql_with_params` -+- Reporter: Paolo | Owner: nobody Melchiorre | Type: New| Status:

Re: [Django] #34609: Deprecate format_html calls without args or kwargs

#34609: Deprecate format_html calls without args or kwargs -+- Reporter: Adam Johnson |Owner: Bhuvnesh Type: | Status: assigned

Re: [Django] #34609: Deprecate format_html calls without args or kwargs

#34609: Deprecate format_html calls without args or kwargs --+ Reporter: Adam Johnson |Owner: Bhuvnesh Type: Cleanup/optimization | Status: assigned

Re: [Django] #34609: Deprecate format_html calls without args or kwargs

#34609: Deprecate format_html calls without args or kwargs --+ Reporter: Adam Johnson |Owner: Bhuvnesh Type: Cleanup/optimization | Status: assigned

Re: [Django] #34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE

#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE --+-- Reporter: Willem Van Onsem |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #34629: AttributeError when using filter argument with Collect in GeoDjango Aggregate

#34629: AttributeError when using filter argument with Collect in GeoDjango Aggregate -+- Reporter: Olivier Le Thanh |Owner: Olivier Duong | Le Thanh Duong

Re: [Django] #34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE

#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE --+-- Reporter: Willem Van Onsem |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE

#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE --+-- Reporter: Willem Van Onsem |Owner: nobody Type: Uncategorized | Status: closed Component:

Re: [Django] #34629: AttributeError when using filter argument with Collect in GeoDjango Aggregate

#34629: AttributeError when using filter argument with Collect in GeoDjango Aggregate -+- Reporter: Olivier Le Thanh |Owner: Olivier Duong | Le Thanh Duong

Re: [Django] #34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE

#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE --+-- Reporter: Willem Van Onsem |Owner: nobody Type: Uncategorized | Status: closed Component:

[Django] #34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE

#34635: ModelChoiceField with a to_attr that can have an EMPTY_VALUE + Reporter: Willem Van Onsem | Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods -+- Reporter: Ram Rachum |Owner: Furkan | Karataş

Re: [Django] #34631: Expression.identity() performance

#34631: Expression.identity() performance -+- Reporter: Blaž Šnuderl |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #34631: Expression.identity() performance

#34631: Expression.identity() performance -+- Reporter: Blaž Šnuderl |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: Akash | Kumar Sen Type: Bug |

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz Felisiak |Owner: nobody Type: Bug | Status: new Component: Database

[Django] #34634: Creating objects with nested MTI crashes.

#34634: Creating objects with nested MTI crashes. -+- Reporter: Mariusz| Owner: nobody Felisiak | Type: Bug| Status: new