Re: [Django] #25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError

#25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError -+- Reporter: MrYoda |Owner: nobody Type: Bug |

Re: [Django] #8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole queryset.

#8065: Calling queyset.in_bulk (without any arguments) should evaluate the whole queryset. -+- Reporter: ElliottM |Owner: bxm156 Type: New feature |

Re: [Django] #25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError

#25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError -+- Reporter: MrYoda |Owner: nobody Type: Bug |

[Django] #25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError

#25987: Creating new object on adminsite with child model inlines and unique_together raises IntegrityError + Reporter: MrYoda | Owner: nobody Type: Bug | Status: new Component: Forms |Version:

Re: [Django] #5698: sqlite backend missing foreign keys

#5698: sqlite backend missing foreign keys -+- Reporter: davisp |Owner: nobody Type: Uncategorized| Status: closed Component: Database layer

[Django] #25986: RFC 6532 support for e-mail

#25986: RFC 6532 support for e-mail -+ Reporter: sergei-maertens | Owner: nobody Type: Bug | Status: new Component: Core (Mail) |Version: 1.9 Severity: Normal | Keywords:

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

#25465: Line breaks in readonly field in admin tabular inline + Reporter: pcraston|Owner: nobody Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #25854: Remove deprecated usage of template.render() with RequestContext in docs

#25854: Remove deprecated usage of template.render() with RequestContext in docs ---+- Reporter: stephanm |Owner: alasdairnicol Type: Bug| Status: new

Re: [Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ -+- Reporter: knbk |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ -+- Reporter: knbk |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

#25465: Line breaks in readonly field in admin tabular inline + Reporter: pcraston|Owner: nobody Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #25982: Djago ORM. Filter using multi-valued queryset

#25982: Djago ORM. Filter using multi-valued queryset -+- Reporter: FreddieFruitSticks |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + "/"

#25971: BrokenLinkEmailsMiddleware shouldn't report 404s when URL = Referer + "/" --+ Reporter: jribbens |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ -+- Reporter: knbk |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #13614: selectfilter2 many to many widget data loss when using the back button

#13614: selectfilter2 many to many widget data loss when using the back button ---+ Reporter: minarets |Owner: julien Type: Bug| Status: new Component:

Re: [Django] #13614: selectfilter2 many to many widget data loss when using the back button (was: selectfilter2 many to many widget data loss with browser issues)

#13614: selectfilter2 many to many widget data loss when using the back button ---+ Reporter: minarets |Owner: julien Type: Bug| Status: new Component:

Re: [Django] #25652: Provide a more generic way to test different browsers in selenium tests

#25652: Provide a more generic way to test different browsers in selenium tests ---+- Reporter: timgraham |Owner: nobody Type: New feature| Status: closed

Re: [Django] #25652: Provide a more generic way to test different browsers in selenium tests

#25652: Provide a more generic way to test different browsers in selenium tests ---+ Reporter: timgraham |Owner: nobody Type: New feature| Status: new

Re: [Django] #25465: Line breaks in readonly field in admin tabular inline

#25465: Line breaks in readonly field in admin tabular inline + Reporter: pcraston|Owner: nobody Type: Bug | Status: new Component: contrib.admin |

Re: [Django] #13008: @never_cache decorator should add 'no-cache' & 'no-store'

#13008: @never_cache decorator should add 'no-cache' & 'no-store' -+- Reporter: harm |Owner: mbertheau Type: Bug | Status: closed

Re: [Django] #13008: @never_cache decorator should add 'no-cache' & 'no-store'

#13008: @never_cache decorator should add 'no-cache' & 'no-store' -+- Reporter: harm |Owner: mbertheau Type: Bug | Status: closed

Re: [Django] #13008: @never_cache decorator should add 'no-cache' & 'no-store'

#13008: @never_cache decorator should add 'no-cache' & 'no-store' -+- Reporter: harm |Owner: mbertheau Type: Bug | Status: closed

Re: [Django] #25746: Isolate inlined test models

#25746: Isolate inlined test models -+- Reporter: charettes|Owner: charettes Type: | Status: assigned Cleanup/optimization

Re: [Django] #25967: TabularInline headers don't have good indication for whether or not a field is required

#25967: TabularInline headers don't have good indication for whether or not a field is required --+ Reporter: timgraham |Owner: akki Type: Cleanup/optimization |

Re: [Django] #25980: Wrong handling of initial value on disabled ModelMultipleChoiceField

#25980: Wrong handling of initial value on disabled ModelMultipleChoiceField ---+-- Reporter: karyon |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #25975: sqlmigrate for pending migrations

#25975: sqlmigrate for pending migrations -+-- Reporter: stylesen |Owner: nobody Type: New feature | Status: new Component: Migrations | Version:

Re: [Django] #25985: Update signature of ModelAdmin.formfield_for_* to make request a positional argument (was: Update signature of ModelAdmin.forrmfield_for_* to make request a positional argument)

#25985: Update signature of ModelAdmin.formfield_for_* to make request a positional argument -+- Reporter: timgraham|Owner: timgraham Type: |

[Django] #25985: Update signature of ModelAdmin.forrmfield_for_* to make request a positional argument

#25985: Update signature of ModelAdmin.forrmfield_for_* to make request a positional argument -+- Reporter: timgraham | Owner: timgraham Type: | Status: new

Re: [Django] #25959: Update logging example to use the django logger

#25959: Update logging example to use the django logger -+- Reporter: SimonSteinberger |Owner: Type: | PramodBisht Cleanup/optimization |

Re: [Django] #25959: Update logging example to use the django logger

#25959: Update logging example to use the django logger -+- Reporter: SimonSteinberger |Owner: Type: | PramodBisht Cleanup/optimization |

Re: [Django] #25748: Glossary: Project vs App

#25748: Glossary: Project vs App --+ Reporter: guettli |Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |

Re: [Django] #25967: TabularInline headers don't have good indication for whether or not a field is required

#25967: TabularInline headers don't have good indication for whether or not a field is required --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25967: TabularInline headers don't have good indication for whether or not a field is required

#25967: TabularInline headers don't have good indication for whether or not a field is required --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #25981: Document the necessity to add on_delete param to old migrations

#25981: Document the necessity to add on_delete param to old migrations -+- Reporter: karyon |Owner: Cheglader Type: | Status: closed

Re: [Django] #25981: Document the necessity to add on_delete param to old migrations

#25981: Document the necessity to add on_delete param to old migrations -+- Reporter: karyon |Owner: Cheglader Type: | Status: closed

Re: [Django] #25972: Filtering a ForeignObject with 'isnull' lookup fails in Django 1.9

#25972: Filtering a ForeignObject with 'isnull' lookup fails in Django 1.9 -+- Reporter: tomo-otsuka |Owner: nobody Type: Bug | Status: closed

Re: [Django] #25972: Filtering a ForeignObject with 'isnull' lookup fails in Django 1.9

#25972: Filtering a ForeignObject with 'isnull' lookup fails in Django 1.9 -+- Reporter: tomo-otsuka |Owner: nobody Type: Bug | Status: closed

Re: [Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ -+- Reporter: knbk |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25983: annotate migrations with Django version

#25983: annotate migrations with Django version ---+-- Reporter: sir-sigurd |Owner: sir-sigurd Type: Uncategorized | Status: assigned Component: Migrations |

Re: [Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ -+- Reporter: knbk |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #25967: TabularInline headers don't have good indication for whether or not a field is required

#25967: TabularInline headers don't have good indication for whether or not a field is required --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization |

[Django] #25984: Incorrect error message in ModelBase.__new__

#25984: Incorrect error message in ModelBase.__new__ --+ Reporter: knbk | Owner: nobody Type: Cleanup/optimization | Status: new Component: Database layer (models, ORM)

Re: [Django] #25967: TabularInline headers don't have good indication for whether or not a field is required

#25967: TabularInline headers don't have good indication for whether or not a field is required --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #24067: Renaming models prompts for content type deletions

#24067: Renaming models prompts for content type deletions -+- Reporter: doepunk |Owner: nobody Type: | Status: new

[Django] #25983: annotate migrations with Django version

#25983: annotate migrations with Django version ---+ Reporter: sir-sigurd | Owner: nobody Type: Uncategorized | Status: new Component: Migrations |Version: 1.9 Severity: Normal | Keywords:

Re: [Django] #24506: Migrations are crashing after changing foreign key from auth.Group model to a proxy model of auth.Group

#24506: Migrations are crashing after changing foreign key from auth.Group model to a proxy model of auth.Group +-- Reporter: tinloaf |Owner: marcofucci Type: Bug |

Re: [Django] #12990: New Field Type: JSONField

#12990: New Field Type: JSONField -+- Reporter: paltman |Owner: nobody Type: New feature | Status: closed Component: Database layer |