Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

#10811: Assigning unsaved model to a ForeignKey leads to silent failures -+- Reporter: Glenn|Owner: | anubhav9042 Type: Bug

Re: [Django] #24784: Admin interface ForeignKey field select widget partially hidden in Firefox

#24784: Admin interface ForeignKey field select widget partially hidden in Firefox -+ Reporter: hobbsd |Owner: nobody Type: Bug | Status: closed

Re: [Django] #24784: Admin interface ForeignKey field select widget partially hidden in Firefox

#24784: Admin interface ForeignKey field select widget partially hidden in Firefox -+ Reporter: hobbsd |Owner: nobody Type: Bug | Status: closed

Re: [Django] #24823: FileField with callable default raise error with forms

#24823: FileField with callable default raise error with forms -+- Reporter: ymph |Owner: nobody Type: Bug | Status: new Component:

[Django] #24823: FileField with callable default raise error with forms

#24823: FileField with callable default raise error with forms -+- Reporter: ymph | Owner: nobody Type: Bug | Status: new Component: Database layer |

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

#10811: Assigning unsaved model to a ForeignKey leads to silent failures -+- Reporter: Glenn|Owner: | anubhav9042 Type: Bug

Re: [Django] #24652: SimpleTestCase should prevent execution of database queries

#24652: SimpleTestCase should prevent execution of database queries -+- Reporter: charettes|Owner: charettes Type: | Status: assigned

[Django] #24822: DateTimeField timezone issue converting default fields

#24822: DateTimeField timezone issue converting default fields --+ Reporter: camiloforero | Owner: nobody Type: Bug | Status: new Component: Migrations|Version: 1.8 Severity: Normal|

Re: [Django] #24820: Add functionality to handle keyboard prompts during migrations for automated deployments

#24820: Add functionality to handle keyboard prompts during migrations for automated deployments -+- Reporter: Protosac |Owner: nobody Type: New feature |

[Django] #24821: migration file very long name

#24821: migration file very long name --+ Reporter: jeanmarcosdarosa | Owner: nobody Type: Bug | Status: new Component: Uncategorized |Version: 1.8 Severity: Normal|

Re: [Django] #24821: migration file very long name

#24821: migration file very long name --+-- Reporter: jeanmarcosdarosa |Owner: nobody Type: Bug | Status: new Component: Uncategorized |

[Django] #24820: Add functionality to handle keyboard prompts during migrations for automated deployments

#24820: Add functionality to handle keyboard prompts during migrations for automated deployments -+- Reporter: Protosac | Owner: nobody Type: New feature | Status: new Component: Migrations

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

#10811: Assigning unsaved model to a ForeignKey leads to silent failures -+- Reporter: Glenn|Owner: | anubhav9042 Type: Bug

Re: [Django] #24813: Document that {% include %} suppresses errors when DEBUG=False

#24813: Document that {% include %} suppresses errors when DEBUG=False --+ Reporter: pratyushmittal|Owner: akulakov Type: Cleanup/optimization | Status: assigned

Re: [Django] #24705: Exception when negating Q object in annotate

#24705: Exception when negating Q object in annotate -+- Reporter: karyon |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL -+ Reporter: murfi|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24819: clearsessions deletes sessions that expire in the next hour (was: Commands provided for clearsessions. It also clears the the last hour and minute session)

#24819: clearsessions deletes sessions that expire in the next hour -+- Reporter: ghanshyam- |Owner: nobody rajpurohit | Type: Bug |

Re: [Django] #24705: Exception when negating Q object in annotate

#24705: Exception when negating Q object in annotate -+- Reporter: karyon |Owner: nobody Type: Bug | Status: new Component: Database

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: closed

Re: [Django] #24553: Pass application list to more admin views

#24553: Pass application list to more admin views ---+ Reporter: rm_|Owner: nobody Type: New feature| Status: closed Component: contrib.admin |

Re: [Django] #24553: Pass application list to more admin views

#24553: Pass application list to more admin views ---+ Reporter: rm_|Owner: nobody Type: New feature| Status: new Component: contrib.admin |

Re: [Django] #24816: Clarify docs about preventing duplicate signals (was: Preventing duplicate signals)

#24816: Clarify docs about preventing duplicate signals --+ Reporter: timkofu |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL -+ Reporter: murfi|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #10811: Assigning unsaved model to a ForeignKey leads to silent failures

#10811: Assigning unsaved model to a ForeignKey leads to silent failures -+- Reporter: Glenn|Owner: | anubhav9042 Type: Bug

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL +-- Reporter: murfi |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL +-- Reporter: murfi |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL +-- Reporter: murfi |Owner: nobody Type: Bug | Status: closed Component:

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL +-- Reporter: murfi |Owner: nobody Type: Bug | Status: closed Component:

[Django] #24819: Commands provided for clearsessions. It also clears the the last hour and minute session

#24819: Commands provided for clearsessions. It also clears the the last hour and minute session --+ Reporter: ghanshyam-rajpurohit | Owner: nobody Type: Bug | Status: new

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24818: models.CharField shouldn't accept a string as max_length (was: models.CharField shouldn't accept a string as max_lenght)

#24818: models.CharField shouldn't accept a string as max_length -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24818: models.CharField shouldn't accept a string as max_lenght

#24818: models.CharField shouldn't accept a string as max_lenght -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #24553: Pass application list to more admin views

#24553: Pass application list to more admin views ---+ Reporter: rm_|Owner: nobody Type: New feature| Status: new Component: contrib.admin |

Re: [Django] #24818: models.CharField shouldn't accept a string as max_lenght

#24818: models.CharField shouldn't accept a string as max_lenght -+- Reporter: slamora |Owner: nobody Type: Bug | Status: new Component:

[Django] #24818: models.CharField shouldn't accept a string as max_lenght

#24818: models.CharField shouldn't accept a string as max_lenght --+ Reporter: slamora | Owner: nobody Type: Bug | Status: new Component: Database layer

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL +-- Reporter: murfi |Owner: nobody Type: Bug | Status: new Component: Migrations

Re: [Django] #24816: Preventing duplicate signals

#24816: Preventing duplicate signals -+- Reporter: timkofu |Owner: nobody Type: | Status: closed Cleanup/optimization |

Re: [Django] #24816: Preventing duplicate signals

#24816: Preventing duplicate signals -+- Reporter: timkofu |Owner: nobody Type: | Status: closed Cleanup/optimization |

[Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL + Reporter: murfi | Owner: nobody Type: Bug | Status: new Component: Migrations |Version: 1.8 Severity: Normal

Re: [Django] #24816: Preventing duplicate signals

#24816: Preventing duplicate signals -+- Reporter: timkofu |Owner: nobody Type: | Status: closed Cleanup/optimization |

[Django] #24816: Preventing duplicate signals

#24816: Preventing duplicate signals --+- Reporter: timkofu | Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) |Version: 1.8 Severity: Normal

Re: [Django] #17085: Deprecate "add_to_builtins" and turn builtins into a property of Engine

#17085: Deprecate "add_to_builtins" and turn builtins into a property of Engine -+ Reporter: carljm |Owner: nobody Type: New feature | Status: new