django-updates
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
Re: [Django] #36056: Fix ignored exceptions in OutputWrapper.flush()
Django
[Django] #36055: Object tools CSS makes buttons cover part of the h2 title when the latter occupies multiple lines
Django
Re: [Django] #36053: FilteredSelectMultiple label to the right of widget on a ModelMultipleChoiceField
Django
Re: [Django] #36053: FilteredSelectMultiple label to the right of widget on a ModelMultipleChoiceField (was: Django Admin Widget FilteredSelectMultiple CSS Not Working)
Django
Re: [Django] #36054: Add schemes parameter to URLField for custom URL scheme validation
Django
Re: [Django] #36054: Add schemes parameter to URLField for custom URL scheme validation
Django
Re: [Django] #36054: Add schemes parameter to URLField for custom URL scheme validation
Django
Re: [Django] #36054: Add schemes parameter to URLField for custom URL scheme validation
Django
Re: [Django] #36054: Add schemes parameter to URLField for custom URL scheme validation (was: Support schemes parameter to URLField for custom URL scheme validation)
Django
[Django] #36054: Support schemes parameter to URLField for custom URL scheme validation
Django
Re: [Django] #36053: Django Admin Widget FilteredSelectMultiple CSS Not Working
Django
[Django] #36053: Django Admin Widget FilteredSelectMultiple CSS Not Working
Django
Re: [Django] #36053: Django Admin Widget FilteredSelectMultiple CSS Not Working
Django
Re: [Django] #36053: Django Admin Widget FilteredSelectMultiple CSS Not Working
Django
[Django] #36052: Add support for CompositePrimaryKey in inspectdb
Django
Re: [Django] #36052: Add support for CompositePrimaryKey in inspectdb
Django
Re: [Django] #36052: Add support for CompositePrimaryKey in inspectdb
Django
Re: [Django] #36052: Add support for CompositePrimaryKey in inspectdb
Django
[Django] #36051: Count CompositePrimaryKey field targets toward function arity check
Django
Re: [Django] #36051: Count CompositePrimaryKey field targets toward function arity check
Django
Re: [Django] #36051: Count CompositePrimaryKey field targets toward function arity check
Django
Re: [Django] #36051: Count CompositePrimaryKey field targets toward function arity check
Django
[Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
Re: [Django] #36050: Cannot resolve OuterRef to CompositePrimaryKey
Django
[Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
Re: [Django] #36049: The `upper` template filter should set `is_safe=True`
Django
[Django] #36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a more appropriate exception
Django
Re: [Django] #36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a more appropriate exception
Django
Re: [Django] #36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a more appropriate exception
Django
Re: [Django] #36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a more appropriate exception
Django
Re: [Django] #36048: CompositePrimaryKey lookup guards raise NotSupportedError instead of a more appropriate exception
Django
[Django] #36047: `BaseConnectionHandler.close_all()` doesn't work with async clients
Django
Re: [Django] #36047: `BaseConnectionHandler.close_all()` doesn't work with async clients
Django
Re: [Django] #36047: `BaseConnectionHandler.close_all()` doesn't work with async clients
Django
Re: [Django] #36047: `BaseConnectionHandler.close_all()` doesn't work with async clients
Django
[Django] #36046: Create an index on the combination of ForeignKeys in the ManyToManyField through table?
Django
Re: [Django] #36046: Create an index on the combination of ForeignKeys in the ManyToManyField through table?
Django
Re: [Django] #36046: Create an index on the combination of ForeignKeys in the ManyToManyField through table?
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field
Django
[Django] #36045: Add Support for PostgreSQL Infinity and -Infinity in Date/Time Fields
Django
Re: [Django] #36045: Add Support for PostgreSQL Infinity and -Infinity in Date/Time Fields
Django
Re: [Django] #36045: Add Support for PostgreSQL Infinity and -Infinity in Date/Time Fields
Django
[Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
Re: [Django] #36044: Reusable form templates example lead to a TemplateDoesNotExist error
Django
[Django] #36043: TransactionTestCase erasing migration data when using --keepdb option
Django
Re: [Django] #36043: TransactionTestCase erasing migration data when using --keepdb option
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositePrimaryKey in F and lhs is another field (was: Lookups fail when rhs wraps CompositeForeignKey in F and lhs is another field)
Django
[Django] #36042: Lookups fail when rhs wraps CompositeForeignKey in F and lhs is another field
Django
Re: [Django] #36042: Lookups fail when rhs wraps CompositeForeignKey in F and lhs is another field
Django
[Django] #36041: related_query_name return wrong related_name
Django
Re: [Django] #36041: related_query_name return wrong related_name
Django
Re: [Django] #35980: Make Django release artifacts PEP 625 compliant
Django
Re: [Django] #27466: Use a datepicker widget for Date[Time]RangeField in admin
Django
[Django] #36040: Web Development with Django
Django
Re: [Django] #36040: Web Development with Django
Django
Re: [Django] #35235: ArrayAgg() doesn't return default when filter contains __in=[].
Django
Re: [Django] #35235: ArrayAgg() doesn't return default when filter contains __in=[].
Django
Re: [Django] #24462: Add a new QuerySet operation to use current results as a subquery
Django
Re: [Django] #35146: Add support for annotate after union
Django
Re: [Django] #26739: Backward operation for RemoveField does not allow a default value in case the field is not null.
Django
Re: [Django] #26739: Backward operation for RemoveField does not allow a default value in case the field is not null.
Django
[Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36039: Add command for Fetching all table names and columns
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
[Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #36038: Added a test case for the display_for_field function when a FileField is passed.
Django
Re: [Django] #35289: Chunked transfer encoding is not handled correctly by MultiPartParser
Django
[Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
Re: [Django] #36037: Documentation mentions default primary key being regular IntegerField, not BigAutoField
Django
[Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
Re: [Django] #36036: Support the 4th dimension (M) in the GEOS API
Django
[Django] #36035: Prefetch while annotating the reference of a m2m relation generates duplicated joins
Django
Re: [Django] #36035: Prefetch while annotating the reference of a m2m relation generates duplicated joins
Django
Re: [Django] #36035: Prefetch while annotating the reference of a m2m relation generates duplicated joins
Django
[Django] #36034: ForeignKey to CompositePrimaryKey crashes.
Django
Re: [Django] #36034: ForeignKey to CompositePrimaryKey crashes.
Django
Re: [Django] #36034: ForeignKey to CompositePrimaryKey crashes.
Django
Re: [Django] #36034: ForeignKey to CompositePrimaryKey crashes.
Django
Re: [Django] #36034: ForeignKey to CompositePrimaryKey crashes.
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL
Django
[Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
Re: [Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
Re: [Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
Re: [Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
Re: [Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
Re: [Django] #36033: Getting TypeError: cannot pickle 'dict_values' object Error with Django 4.2.16
Django
[Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
Re: [Django] #36032: Apply a link to the URLField value on the admin app index page.
Django
[Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36031: DecimalRangeField __contains query for a value causes DataError
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns inconsistent decimal places on PostgreSQL (was: Expressions that divide an integer field by a constant decimal.Decimal returns no inconsistent decimal places on PostgreSQL)
Django
Re: [Django] #36030: Expressions that divide an integer field by a constant decimal.Decimal returns no inconsistent decimal places on PostgreSQL (was: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.)
Django
[Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Re: [Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Re: [Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Re: [Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Re: [Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Re: [Django] #36030: Rendering decimal to SQL is incoherent and leads to bugs. It relays on str formating not type.
Django
Earlier messages
Later messages