django-updates
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [Django] #36502: [DJANGO] bulk INSERT is not using UNNEST when a field is a FK on PostgreSQL
Django
Re: [Django] #36502: [DJANGO] bulk INSERT is not using UNNEST when a field is a FK on PostgreSQL
Django
[Django] #36501: Generating Random Test Data for Django Models
Django
Re: [Django] #36501: Generating Random Test Data for Django Models
Django
Re: [Django] #36501: Generating Random Test Data for Django Models
Django
Re: [Django] #36501: Generating Random Test Data for Django Models
Django
[Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
Re: [Django] #36500: pre-commit should enforce 79 char limit for docstrings and comments
Django
[Django] #36499: CPython might have introduced a change of behaviour in their fix for https://github.com/python/cpython/issues/135462
Django
Re: [Django] #36499: CPython might have introduced a change of behaviour in their fix for https://github.com/python/cpython/issues/135462
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #36226: Only PBKDF2PasswordHasher supports str and bytes password
Django
Re: [Django] #8408: Add a new meta option: don't do count(*) in admin
Django
[Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
Re: [Django] #36498: Inline button to add first / only related instance should say "Add ...", not "Add another ..."
Django
[Django] #36497: Add ModelAdmin.estimated_count for faster changelist pagination
Django
Re: [Django] #36497: Add ModelAdmin.estimated_count for faster changelist pagination
Django
Re: [Django] #36497: Add ModelAdmin.estimated_count for faster changelist pagination
Django
Re: [Django] #36497: Add ModelAdmin.estimated_count for faster changelist pagination
Django
[Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #36496: SQLite test database path not recognised when running tests in parallel
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
Re: [Django] #35381: Provide `JSONNull` expression to represent JSON `null` value
Django
[Django] #36495: Bug in determining if template file should be autoreloaded in `django.utils.autoreload.notify_file_changed` ?
Django
Re: [Django] #36495: Bug in determining if template file should be autoreloaded in `django.utils.autoreload.notify_file_changed` ?
Django
[Django] #36494: Various failures for JSONField lookups and right-hand side subqueries
Django
Re: [Django] #36494: Various failures for JSONField lookups and right-hand side subqueries
Django
[Django] #36493: Docs: add clear postgresql user/db setup instructions.
Django
Re: [Django] #36493: Docs: add clear postgresql user/db setup instructions.
Django
Re: [Django] #36493: Docs: add clear postgresql user/db setup instructions.
Django
Re: [Django] #24162: "Method Flowchart" for all CB(G)V documentation pages
Django
[Django] #36492: Sqlite: lack of specificity when querying against booleans hurts the query-optimizer
Django
Re: [Django] #36492: Sqlite: lack of specificity when querying against booleans hurts the query-optimizer
Django
Re: [Django] #36492: Sqlite: lack of specificity when querying against booleans hurts the query-optimizer
Django
Re: [Django] #36492: Sqlite: lack of specificity when querying against booleans hurts the query-optimizer
Django
Re: [Django] #36492: Sqlite: lack of specificity when querying against booleans hurts the query-optimizer
Django
[Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #36491: AttributeError: '_io.TextIOWrapper' object has no attribute 'getvalue' when setUpTestData raises and tests are run with –parallel–buffer
Django
Re: [Django] #27236: Deprecate Model.Meta.index_together in favour of Model.Meta.indexes
Django
Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)
Django
Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)
Django
Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)
Django
[Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
Re: [Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
Re: [Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
Re: [Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
Re: [Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
Re: [Django] #36490: Avoid unnecessary transaction in QuerySet.bulk_create
Django
[Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
Re: [Django] #36489: OneToOneField + concurrent get_or_create results in wrong object in field cache
Django
[Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
Re: [Django] #36488: RedirectView(query_string=True) produces double '?' when both destination URL and request have query parameters
Django
[Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
Re: [Django] #36487: Database on commit error logging fails for partials
Django
[Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
Re: [Django] #36486: Add MongoDB Drivers to the List of 3rd Party Database Backends
Django
[Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
Re: [Django] #36485: Add linting tool for documentation
Django
[Django] #36484: Add optional error-on-integer-overflow setting for QuerySet filters
Django
Re: [Django] #36484: Add optional error-on-integer-overflow setting for QuerySet filters
Django
Re: [Django] #36484: Add optional error-on-integer-overflow setting for QuerySet filters
Django
Re: [Django] #36484: Add optional error-on-integer-overflow setting for QuerySet filters
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side.
Django
Re: [Django] #35453: ManyToMany field incorrectly identified as a concrete field on the defining side. (was: ManyToMany field is a concrete field on the defining side.)
Django
Re: [Django] #36336: Incorrect size of first autocomple in Inlines with "collapse" class (on chromium based browsers?)
Django
Re: [Django] #36336: Incorrect size of first autocomple in Inlines with "collapse" class (on chromium based browsers?)
Django
Re: [Django] #36336: Incorrect size of first autocomple in Inlines with "collapse" class (on chromium based browsers?)
Django
Re: [Django] #36336: Incorrect size of first autocomple in Inlines with "collapse" class (on chromium based browsers?)
Django
Re: [Django] #36336: Incorrect size of first autocomple in Inlines with "collapse" class (on chromium based browsers?)
Django
[Django] #36483: IntegerField will accept non-ASCII digits, which leads to the same page appearing at many URLs
Django
Re: [Django] #36483: IntegerField will accept non-ASCII digits, which leads to the same page appearing at many URLs
Django
Re: [Django] #36483: IntegerField will accept non-ASCII digits, which leads to the same page appearing at many URLs
Django
Earlier messages
Later messages