django-updates  

Messages by Thread

• • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
  • Re: [Django] #27489: Renaming a model doesn't rename the permission name and codename Django
• [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
  • Re: [Django] #36843: RenamePermission might operate on unrelated models Django
• [Django] #36842: Blank FloatField validation is not run on django admin and value is lost on edition. Django
  • Re: [Django] #36842: Blank FloatField validation is not run on django admin and value is lost on edition. Django
  • Re: [Django] #36842: Blank FloatField validation is not run on django admin and value is lost on edition. Django
• Re: [Django] #29257: If creation of a db cursor fails, the resulting traceback is misleading Django
  • Re: [Django] #29257: If creation of a db cursor fails, the resulting traceback is misleading Django
• [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
  • Re: [Django] #36841: Add multipart_parser_class attribute to HttpRequest for pluggable multipart parsing Django
• Re: [Django] #32779: Add tablespace support to UniqueConstraint class Django
• Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
  • Re: [Django] #36825: CSP nonces are not applied in the Django admin Django
• [Django] #36840: makemigrations not detecting adding UniqueConstraint to models.py Django
  • Re: [Django] #36840: makemigrations not detecting adding UniqueConstraint to models.py Django
  • Re: [Django] #36840: makemigrations not detecting adding UniqueConstraint to models.py Django
  • Re: [Django] #36840: makemigrations not detecting adding UniqueConstraint to models.py Django
  • Re: [Django] #36840: makemigrations not detecting adding UniqueConstraint to models.py Django
• Re: [Django] #20752: Error signals are not reliable, especially when dealing with database errors Django
• Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
  • Re: [Django] #36815: Avoid unnecessary prepare_value calls when inserting db_defaults Django
• Re: [Django] #36166: Backwards migration to replaced migration leads to InconsistentMigrationHistory on forward migrate Django
  • Re: [Django] #36166: Backwards migration to replaced migration leads to InconsistentMigrationHistory on forward migrate Django
  • Re: [Django] #36166: Backwards migration to replaced migration leads to InconsistentMigrationHistory on forward migrate Django
• Re: [Django] #35979: Empty form ErrorList display as square brackets "[]" Django
• Re: [Django] #30149: Empty value selected check in Admin Filter prevents subclassing Django
  • Re: [Django] #30149: Empty value selected check in Admin Filter prevents subclassing Django
  • Re: [Django] #30149: Empty value selected check in Admin Filter prevents subclassing Django
• Re: [Django] #27752: Fix and test admin_order_field set for the __str__ of a model Django
  • Re: [Django] #27752: Fix and test admin_order_field set for the __str__ of a model Django
  • Re: [Django] #27752: Fix and test admin_order_field set for the __str__ of a model Django
  • Re: [Django] #27752: Fix and test admin_order_field set for the __str__ of a model Django
• Re: [Django] #24622: Response "context" and "templates" not available in the Test Client when using Jinja2 - Django 1.8 Django
• Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
  • Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
  • Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
  • Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
  • Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
  • Re: [Django] #32213: QuerySet.values()/.values_list() on KeyTransforms return wrong values for double-quoted strings on SQLite and Oracle Django
• Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
  • Re: [Django] #35442: QuerySet.only() causes n+1 queries with reverse foreign key relation when related id is not included. Django
• Re: [Django] #33586: Applying RunPython backward results in ValueError when involved models are referenced through multiple foreign keys Django
  • Re: [Django] #33586: Applying RunPython backward results in ValueError when involved models are referenced through multiple foreign keys Django
  • Re: [Django] #33586: Applying RunPython backward results in ValueError when involved models are referenced through multiple foreign keys Django
  • Re: [Django] #33586: Applying RunPython backward results in ValueError when involved models are referenced through multiple foreign keys Django
  • Re: [Django] #33586: Applying RunPython backward results in ValueError when involved models are referenced through multiple foreign keys Django
• Re: [Django] #31908: Add parallel testing support to Oracle backend Django
  • Re: [Django] #31908: Add parallel testing support to Oracle backend Django
  • Re: [Django] #31908: Add parallel testing support to Oracle backend Django
  • Re: [Django] #31908: Add parallel testing support to Oracle backend Django
  • Re: [Django] #31908: Add parallel testing support to Oracle backend Django
  • Re: [Django] #31908: Add parallel testing support to Oracle backend Django
• Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
  • Re: [Django] #36837: Client.force_login won't work for permission-only backends inheriting from BaseBackend Django
• Re: [Django] #12157: FileSystemStorage does file I/O inefficiently, despite providing options to permit larger blocksizes Django
• Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
  • Re: [Django] #36784: Add CSP support to Django's script object and media objects Django
• [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
  • Re: [Django] #36839: Renaming of content types on RenameModel operations silently passes when duplicates are found Django
• Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
  • Re: [Django] #36750: dumpdata's output of m2m values is not deterministic Django
• Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated Django
  • Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated Django
  • Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated Django
  • Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated Django
  • Re: [Django] #36793: Reverting a model rename in an environment with pre-Django 6.0 permission records leaves wrong users & groups associated Django
• Re: [Django] #36499: strip_tags() and test_parsing_errors() fails with patched Python versions due to HTMLParser EOF behavior change Django
  • Re: [Django] #36499: strip_tags() and test_parsing_errors() fails with patched Python versions due to HTMLParser EOF behavior change Django
  • Re: [Django] #36499: strip_tags() and test_parsing_errors() fails with patched Python versions due to HTMLParser EOF behavior change Django
  • Re: [Django] #36499: strip_tags() and test_parsing_errors() fails with patched Python versions due to HTMLParser EOF behavior change Django
• Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
  • Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres Django
• Re: [Django] #23533: Hook for default QuerySet filtering defined on the QuerySet itself. Django
• Re: [Django] #36829: ClearableFileInput.use_fieldset became True in Django 6.0 Django
  • Re: [Django] #36829: ClearableFileInput.use_fieldset became True in Django 6.0 Django
  • Re: [Django] #36829: ClearableFileInput.use_fieldset became True in Django 6.0 Django
  • Re: [Django] #36829: ClearableFileInput.use_fieldset became True in Django 6.0 Django
• Re: [Django] #36829: ClearableFileInput.use_fieldset became True in Django 6.0 (was: Missing release note and documentation for change to ClearableFileInput.use_fieldset) Django
• Re: [Django] #36828: Evaluate using <fieldset> on ClearableFileInput Django
  • Re: [Django] #36828: Evaluate using <fieldset> on ClearableFileInput Django
• Re: [Django] #36828: Evaluate using <fieldset> on ClearableFileInput (was: Missing input label (WCAG2.1) on ClearableFileInput) Django
• Re: [Django] #36829: Missing release note and documentation for change to ClearableFileInput.use_fieldset Django
  • Re: [Django] #36829: Missing release note and documentation for change to ClearableFileInput.use_fieldset Django
• Re: [Django] #16260: Ability to change dismissRelatedLookupPopup on custom callback function Django

• Later messages