Re: [Django] #24508: F() object operations do not correcly reflect with annotate

#24508: F() object operations do not correcly reflect with annotate -+- Reporter: mijamo |Owner: jarshwah Type: Bug | Status: assigned C

[Django] #24509: Allow Expressions when saving new models

#24509: Allow Expressions when saving new models --+ Reporter: AlexHill | Owner: nobody Type: New feature | Status: new Component: Database layer (models, ORM) |

Re: [Django] #24508: F() object operations do not correcly reflect with annotate

#24508: F() object operations do not correcly reflect with annotate -+- Reporter: mijamo |Owner: nobody Type: Bug | Status: new Componen

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+ Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #24085: @login_required decorator redirects to a locale specific URL when using i18n_patterns

#24085: @login_required decorator redirects to a locale specific URL when using i18n_patterns -+- Reporter: thedrow |Owner: nobody Type: Bug |

Re: [Django] #24347: parameter 'widget' of BoundField.as_widget is ignored

#24347: parameter 'widget' of BoundField.as_widget is ignored -+- Reporter: srkunze |Owner: nobody Type: Bug | Status: new Component: Fo

Re: [Django] #24285: get_admin_log template tag doesn't work without for_user parameter

#24285: get_admin_log template tag doesn't work without for_user parameter -+- Reporter: yairchu |Owner: nobody Type: | Status: new Cle

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

#24500: Django runtests - 3 tests fail on windows due to encoding troubles --+ Reporter: pakal |Owner: nobody Type: Bug | Status: new

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

#24500: Django runtests - 3 tests fail on windows due to encoding troubles --+ Reporter: pakal |Owner: nobody Type: Bug | Status: new

Re: [Django] #24508: F() object operations do not correcly reflect with annotate (was: F() object operations correcly reflecting with annotate)

#24508: F() object operations do not correcly reflect with annotate -+- Reporter: mijamo |Owner: nobody Type: Bug | Status: new Componen

[Django] #24508: F() object operations correcly reflecting with annotate

#24508: F() object operations correcly reflecting with annotate --+ Reporter: mijamo| Owner: nobody Type: Bug | Status: new Component: Database layer (mo

Re: [Django] #24469: Revisit strategy of escaping Django's form elements in non-Django forms

#24469: Revisit strategy of escaping Django's form elements in non-Django forms -+- Reporter: MoritzS |Owner: aaugustin Type: | Status: a

Re: [Django] #24470: Serialization of base classes is not customizable for migrations

#24470: Serialization of base classes is not customizable for migrations -+ Reporter: rockymeza|Owner: nobody Type: New feature | Status: new Component: Migrations |

Re: [Django] #24472: Define internal types explicitly for related fields

#24472: Define internal types explicitly for related fields -+- Reporter: coldmind |Owner: coldmind Type: New feature | Status: new Component: Da

Re: [Django] #24506: Proxying User model creates an invalid migration

#24506: Proxying User model creates an invalid migration -+- Reporter: tinloaf |Owner: nobody Type: Bug | Status: new Component: Databas

Re: [Django] #24507: Add the possibility to create only one index on CharField

#24507: Add the possibility to create only one index on CharField -+- Reporter: rodo |Owner: nobody Type: | Status: closed Cleanup/o

Re: [Django] #24507: Add the possibility to create only one index on CharField

#24507: Add the possibility to create only one index on CharField -+- Reporter: rodo |Owner: nobody Type: | Status: closed Cleanup/o

Re: [Django] #24502: Using non model fields in an admin ModelForm does not work if the field is listed in fieldsets (and fields I think)

#24502: Using non model fields in an admin ModelForm does not work if the field is listed in fieldsets (and fields I think) ---+-- Reporter: bdauvergne |Owner: nobody Type: Uncategorized |

Re: [Django] #24507: Add the possibility to create only one index on CharField

#24507: Add the possibility to create only one index on CharField -+- Reporter: rodo |Owner: nobody Type: | Status: new Cleanup/opti

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+ Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #24507: Add the possibility to create only one index on CharField

#24507: Add the possibility to create only one index on CharField -+- Reporter: rodo |Owner: nobody Type: | Status: new Cleanup/opti

Re: [Django] #24483: keepdb migrations break choices as generators

#24483: keepdb migrations break choices as generators -+- Reporter: davidszotten |Owner: Type: Bug | Status: new Component: Migrations

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+-- Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #14645: Exclude query with multiple conditions for the same multi-value relation not correct

#14645: Exclude query with multiple conditions for the same multi-value relation not correct -+- Reporter: Ben Buchwald |Owner: nobody | Type: Bug

[Django] #24507: Add the possibility to create only one index on CharField

#24507: Add the possibility to create only one index on CharField --+ Reporter: rodo | Owner: nobody Type: Cleanup/optimization | Status: new Component: Database layer (

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+-- Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+-- Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN

#24496: Check CSRF Referer against CSRF_COOKIE_DOMAIN --+-- Reporter: mattrobenolt |Owner: nobody Type: New feature | Status: new Component: CSRF |

Re: [Django] #15667: Implement template-based widget rendering

#15667: Implement template-based widget rendering + Reporter: brutasse|Owner: brutasse Type: New feature | Status: new Component: Forms |

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

#24500: Django runtests - 3 tests fail on windows due to encoding troubles --+ Reporter: pakal |Owner: nobody Type: Bug | Status: new

[Django] #24506: Proxying User model creates an invalid migration

#24506: Proxying User model creates an invalid migration --+ Reporter: tinloaf | Owner: nobody Type: Bug | Status: new Component: Database layer (models, O

Re: [Django] #24417: Add ModelAdmin.get_list_select_related()

#24417: Add ModelAdmin.get_list_select_related() -+- Reporter: eskhool |Owner: gannetson Type: New feature | Status: closed Component: contrib.a

Re: [Django] #24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly

#24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly -+- Reporter: gergelypolonkai |Owner: nobody Type: Bug |

Re: [Django] #24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly

#24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly -+- Reporter: gergelypolonkai |Owner: nobody Type: Bug |

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

#24500: Django runtests - 3 tests fail on windows due to encoding troubles --+ Reporter: pakal |Owner: nobody Type: Bug | Status: new

[Django] #24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly

#24505: Multiple ManyToManyFields to same "to" model with related_name set to '+' mix up badly --+ Reporter: gergelypolonkai | Owner: nobody Type: Bug | Status: new

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

#24500: Django runtests - 3 tests fail on windows due to encoding troubles -+- Reporter: pakal|Owner: nobody Type: Bug | Status: new C

Re: [Django] #11365: django.db.models.fields.EmailField max_length should be 254

#11365: django.db.models.fields.EmailField max_length should be 254 -+- Reporter: shellsage|Owner: nobody Type: Uncategorized| Status: closed Compo

Re: [Django] #15180: reverse doesn't check default_args

#15180: reverse doesn't check default_args -+- Reporter: olaf |Owner: nobody Type: New feature | Status: closed Component: Core (URLs)