Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: Alberto |

Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: Alberto |

Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: Alberto |

Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: Alberto |

Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: nobody Type: Bug |

Re: [Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto Misail |Owner: nobody Type: Bug |

[Django] #29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char)

#29194: Saving entry into db fails when value of a textfield type parameter is too big (more than 6000 char) -+- Reporter: Alberto| Owner: nobody Misail |

Re: [Django] #29188: ContentFile.size remains constant after initializing

#29188: ContentFile.size remains constant after initializing -+- Reporter: Maksim Iakovlev |Owner: Alex | Stovbur Type: Bug |

Re: [Django] #28943: Avoid the need to call get_context_data() in TemplateView subclasses

#28943: Avoid the need to call get_context_data() in TemplateView subclasses -+- Reporter: James Pic|Owner: nobody Type: | Status: closed

Re: [Django] #28645: AuthenticationForm's inactive user error isn't raised when using ModelBackend

#28645: AuthenticationForm's inactive user error isn't raised when using ModelBackend -+- Reporter: Guilherme Junqueira |Owner: | shangdahao Type: Bug

Re: [Django] #28645: AuthenticationForm's inactive user error isn't raised when using ModelBackend

#28645: AuthenticationForm's inactive user error isn't raised when using ModelBackend -+- Reporter: Guilherme Junqueira |Owner: | shangdahao Type: Bug

Re: [Django] #29192: Docs on abstract base models say you can't override abstract fields

#29192: Docs on abstract base models say you can't override abstract fields +-- Reporter: Marten Kenbeek |Owner: klee05 Type: Bug | Status: assigned

[Django] #29193: Altering a field with a unique constraint drops and rebuilds FKs to other fields in the table

#29193: Altering a field with a unique constraint drops and rebuilds FKs to other fields in the table -+ Reporter: Jeremy Bowman | Owner: nobody Type: Bug| Status:

Re: [Django] #29191: Move the model name to the beginning of the page title for admin add/change/delete pages (was: Admin page title)

#29191: Move the model name to the beginning of the page title for admin add/change/delete pages -+- Reporter: Dmitrij Strelnikov |Owner: nobody Type: |

[Django] #29192: Docs on abstract base models say you can't override abstract fields

#29192: Docs on abstract base models say you can't override abstract fields --+ Reporter: Marten Kenbeek | Owner: nobody Type: Bug | Status: new

[Django] #29191: Admin page title

#29191: Admin page title + Reporter: Dmitrij Strelnikov| Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.admin |

Re: [Django] #29170: Oracle - Unable to add triggers in migrations, semicolon removed.

#29170: Oracle - Unable to add triggers in migrations, semicolon removed. -+- Reporter: Danny Willems|Owner: nobody Type: Bug | Status: closed

Re: [Django] #29190: timezone.is_aware() raises unhandled exception when receiving datetime.date object as argument

#29190: timezone.is_aware() raises unhandled exception when receiving datetime.date object as argument -+- Reporter: Dariem Pérez |Owner: nobody Herrera|

[Django] #29190: timezone.is_aware() raises unhandled exception when receiving datetime.date object as argument

#29190: timezone.is_aware() raises unhandled exception when receiving datetime.date object as argument -+- Reporter: Dariem | Owner: nobody Pérez Herrera |

Re: [Django] #25367: Allow expressions in .filter() calls

#25367: Allow expressions in .filter() calls -+- Reporter: Anssi Kääriäinen |Owner: Matthew Type: | Schinckel Cleanup/optimization |

Re: [Django] #29120: Document that the admin autocomplete requires the change permission of the related model

#29120: Document that the admin autocomplete requires the change permission of the related model -+- Reporter: Rodrigo Pinheiro |Owner: Johannes Marques de Araújo | Hoppe

Re: [Django] #22449: Colorize output of test results

#22449: Colorize output of test results -+- Reporter: Jake Rothenbuhler|Owner: Yuri | Shikanov Type: New feature |

Re: [Django] #22449: Colorize output of test results

#22449: Colorize output of test results -+- Reporter: Jake Rothenbuhler|Owner: Yuri | Shikanov Type: New feature |