repo string | instance_id string | base_commit string | patch string | test_patch string | problem_statement string | hints_text string | created_at string | version string | FAIL_TO_PASS string | PASS_TO_PASS string | environment_setup_commit string |
|---|---|---|---|---|---|---|---|---|---|---|---|
django/django | django__django-11001 | ef082ebb84f00e38af4e8880d04e8365c2766d34 | diff --git a/django/db/models/sql/compiler.py b/django/db/models/sql/compiler.py
--- a/django/db/models/sql/compiler.py
+++ b/django/db/models/sql/compiler.py
@@ -32,7 +32,8 @@ def __init__(self, query, connection, using):
self.select = None
self.annotation_col_map = None
self.klass_info = No... | diff --git a/tests/expressions/tests.py b/tests/expressions/tests.py
--- a/tests/expressions/tests.py
+++ b/tests/expressions/tests.py
@@ -384,6 +384,29 @@ def test_order_by_exists(self):
)
self.assertSequenceEqual(mustermanns_by_seniority, [self.max, mary])
+ def test_order_by_multiline_sql(self... | Incorrect removal of order_by clause created as multiline RawSQL
Description
Hi.
The SQLCompiler is ripping off one of my "order by" clause, because he "thinks" the clause was already "seen" (in SQLCompiler.get_order_by()). I'm using expressions written as multiline RawSQLs, which are similar but not the same.
The b... | Is there a reason you can't use conditional expressions, e.g. something like: MyModel.objects.annotate( custom_order=Case( When(...), ) ).order_by('custom_order') I'm thinking that would avoid fiddly ordering_parts regular expression. If there's some shortcoming to that approach, it might be easier to address that. Al... | 2019-02-17T13:02:09Z | 3.0 | ["test_order_by_multiline_sql (expressions.tests.BasicExpressionsTests)", "test_order_of_operations (expressions.tests.BasicExpressionsTests)"] | ["test_deconstruct (expressions.tests.FTests)", "test_deepcopy (expressions.tests.FTests)", "test_equal (expressions.tests.FTests)", "test_hash (expressions.tests.FTests)", "test_not_equal_Value (expressions.tests.FTests)", "test_and (expressions.tests.CombinableTests)", "test_negation (expressions.tests.CombinableTest... | 419a78300f7cd27611196e1e464d50fd0385ff27 |
django/django | django__django-11999 | 84633905273fc916e3d17883810d9969c03f73c2 | diff --git a/django/db/models/fields/__init__.py b/django/db/models/fields/__init__.py
--- a/django/db/models/fields/__init__.py
+++ b/django/db/models/fields/__init__.py
@@ -763,8 +763,12 @@ def contribute_to_class(self, cls, name, private_only=False):
if not getattr(cls, self.attname, None):
... | diff --git a/tests/model_fields/tests.py b/tests/model_fields/tests.py
--- a/tests/model_fields/tests.py
+++ b/tests/model_fields/tests.py
@@ -168,6 +168,16 @@ def test_get_FIELD_display_translated(self):
self.assertIsInstance(val, str)
self.assertEqual(val, 'translated')
+ def test_overriding_FI... | Cannot override get_FOO_display() in Django 2.2+.
Description
I cannot override the get_FIELD_display function on models since version 2.2. It works in version 2.1.
Example:
class FooBar(models.Model):
foo_bar = models.CharField(_("foo"), choices=[(1, 'foo'), (2, 'bar')])
def __str__(self):
return self.get_foo_ba... | Thanks for this report. Regression in a68ea231012434b522ce45c513d84add516afa60. Reproduced at 54a7b021125d23a248e70ba17bf8b10bc8619234.
OK, I have a lead on this. Not at all happy about how it looks at first pass, but I'll a proof of concept PR together for it tomorrow AM.
I don't think it should be marked as blocker s... | 2019-10-31T10:39:18Z | 3.1 | ["test_overriding_FIELD_display (model_fields.tests.GetFieldDisplayTests)"] | ["test_blank_in_choices (model_fields.tests.GetChoicesTests)", "test_blank_in_grouped_choices (model_fields.tests.GetChoicesTests)", "test_empty_choices (model_fields.tests.GetChoicesTests)", "test_lazy_strings_not_evaluated (model_fields.tests.GetChoicesTests)", "test_check (model_fields.tests.ChoicesTests)", "test_ch... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-12184 | 5d674eac871a306405b0fbbaeb17bbeba9c68bf3 | diff --git a/django/urls/resolvers.py b/django/urls/resolvers.py
--- a/django/urls/resolvers.py
+++ b/django/urls/resolvers.py
@@ -158,8 +158,9 @@ def match(self, path):
# If there are any named groups, use those as kwargs, ignoring
# non-named groups. Otherwise, pass all non-named arguments a... | diff --git a/tests/urlpatterns/path_urls.py b/tests/urlpatterns/path_urls.py
--- a/tests/urlpatterns/path_urls.py
+++ b/tests/urlpatterns/path_urls.py
@@ -12,6 +12,11 @@
path('included_urls/', include('urlpatterns.included_urls')),
re_path(r'^regex/(?P<pk>[0-9]+)/$', views.empty_view, name='regex'),
re_p... | Optional URL params crash some view functions.
Description
My use case, running fine with Django until 2.2:
URLConf:
urlpatterns += [
...
re_path(r'^module/(?P<format>(html|json|xml))?/?$', views.modules, name='modules'),
]
View:
def modules(request, format='html'):
...
return render(...)
With Django 3.0, this is... | Tracked regression in 76b993a117b61c41584e95149a67d8a1e9f49dd1.
It seems to work if you remove the extra parentheses: re_path(r'^module/(?P<format>html|json|xml)?/?$', views.modules, name='modules'), It seems Django is getting confused by the nested groups. | 2019-12-05T13:09:48Z | 3.1 | ["test_re_path_with_missing_optional_parameter (urlpatterns.tests.SimplifiedURLTests)"] | ["test_allows_non_ascii_but_valid_identifiers (urlpatterns.tests.ParameterRestrictionTests)", "test_non_identifier_parameter_name_causes_exception (urlpatterns.tests.ParameterRestrictionTests)", "test_matching_urls (urlpatterns.tests.ConverterTests)", "test_nonmatching_urls (urlpatterns.tests.ConverterTests)", "test_re... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-12113 | 62254c5202e80a68f4fe6572a2be46a3d953de1a | diff --git a/django/db/backends/sqlite3/creation.py b/django/db/backends/sqlite3/creation.py
--- a/django/db/backends/sqlite3/creation.py
+++ b/django/db/backends/sqlite3/creation.py
@@ -98,4 +98,6 @@ def test_db_signature(self):
sig = [self.connection.settings_dict['NAME']]
if self.is_in_memory_db(te... | diff --git a/tests/backends/sqlite/test_creation.py b/tests/backends/sqlite/test_creation.py
new file mode 100644
--- /dev/null
+++ b/tests/backends/sqlite/test_creation.py
@@ -0,0 +1,18 @@
+import copy
+import unittest
+
+from django.db import connection
+from django.test import SimpleTestCase
+
+
+@unittest.skipUnles... | admin_views.test_multidb fails with persistent test SQLite database.
Description
(last modified by Mariusz Felisiak)
I've tried using persistent SQLite databases for the tests (to make use of
--keepdb), but at least some test fails with:
sqlite3.OperationalError: database is locked
This is not an issue when onl... | This is only an issue when setting TEST["NAME"], but not NAME. The following works: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': 'django_tests_default.sqlite3', }, 'other': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': 'django_tests_other.sqlite3', } }
Reproduced at 0dd2308cf6f559a4f4b... | 2019-11-20T17:49:06Z | 3.1 | ["test_custom_test_name (backends.sqlite.test_creation.TestDbSignatureTests)"] | [] | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-11283 | 08a4ee06510ae45562c228eefbdcaac84bd38c7a | diff --git a/django/contrib/auth/migrations/0011_update_proxy_permissions.py b/django/contrib/auth/migrations/0011_update_proxy_permissions.py
--- a/django/contrib/auth/migrations/0011_update_proxy_permissions.py
+++ b/django/contrib/auth/migrations/0011_update_proxy_permissions.py
@@ -1,5 +1,18 @@
-from django.db impo... | diff --git a/tests/auth_tests/test_migrations.py b/tests/auth_tests/test_migrations.py
--- a/tests/auth_tests/test_migrations.py
+++ b/tests/auth_tests/test_migrations.py
@@ -4,6 +4,7 @@
from django.contrib.auth.models import Permission, User
from django.contrib.contenttypes.models import ContentType
from django.tes... | # Enhanced Problem Statement: Proxy Model Permission Migration Failure
## Issue Description
When upgrading a Django project to version 2.2, the migration `auth.0011_update_proxy_permissions` fails with an integrity error when models have been recreated as proxy models. The error occurs because Django attempts to creat... | Please provide a sample project or enough details to reproduce the issue.
Same problem for me. If a Permission exists already with the new content_type and permission name, IntegrityError is raised since it violates the unique_key constraint on permission model i.e. content_type_id_code_name
To get into the situation w... | 2019-04-26T07:02:50Z | 3.0 | ["test_migrate_with_existing_target_permission (auth_tests.test_migrations.ProxyModelWithSameAppLabelTests)"] | ["test_migrate_backwards (auth_tests.test_migrations.ProxyModelWithDifferentAppLabelTests)", "test_proxy_model_permissions_contenttype (auth_tests.test_migrations.ProxyModelWithDifferentAppLabelTests)", "test_user_has_now_proxy_model_permissions (auth_tests.test_migrations.ProxyModelWithDifferentAppLabelTests)", "test_... | 419a78300f7cd27611196e1e464d50fd0385ff27 |
django/django | django__django-11630 | 65e86948b80262574058a94ccaae3a9b59c3faea | diff --git a/django/core/checks/model_checks.py b/django/core/checks/model_checks.py
--- a/django/core/checks/model_checks.py
+++ b/django/core/checks/model_checks.py
@@ -4,7 +4,8 @@
from itertools import chain
from django.apps import apps
-from django.core.checks import Error, Tags, register
+from django.conf impo... | diff --git a/tests/check_framework/test_model_checks.py b/tests/check_framework/test_model_checks.py
--- a/tests/check_framework/test_model_checks.py
+++ b/tests/check_framework/test_model_checks.py
@@ -1,12 +1,16 @@
from django.core import checks
-from django.core.checks import Error
+from django.core.checks import E... | Django throws error when different apps with different models have the same name table name.
Description
Error message:
table_name: (models.E028) db_table 'table_name' is used by multiple models: base.ModelName, app2.ModelName.
We have a Base app that points to a central database and that has its own tables. We then ... | Regression in [5d25804eaf81795c7d457e5a2a9f0b9b0989136c], ticket #20098. My opinion is that as soon as the project has a non-empty DATABASE_ROUTERS setting, the error should be turned into a warning, as it becomes difficult to say for sure that it's an error. And then the project can add the warning in SILENCED_SYSTEM_... | 2019-08-05T11:22:41Z | 3.0 | ["test_collision_across_apps_database_routers_installed (check_framework.test_model_checks.DuplicateDBTableTests)", "test_collision_in_same_app_database_routers_installed (check_framework.test_model_checks.DuplicateDBTableTests)"] | ["test_collision_abstract_model (check_framework.test_model_checks.IndexNameTests)", "test_collision_across_apps (check_framework.test_model_checks.IndexNameTests)", "test_collision_in_different_models (check_framework.test_model_checks.IndexNameTests)", "test_collision_in_same_model (check_framework.test_model_checks.... | 419a78300f7cd27611196e1e464d50fd0385ff27 |
django/django | django__django-11905 | 2f72480fbd27896c986c45193e1603e35c0b19a7 | diff --git a/django/db/models/lookups.py b/django/db/models/lookups.py
--- a/django/db/models/lookups.py
+++ b/django/db/models/lookups.py
@@ -1,5 +1,6 @@
import itertools
import math
+import warnings
from copy import copy
from django.core.exceptions import EmptyResultSet
@@ -9,6 +10,7 @@
)
from django.db.model... | diff --git a/tests/lookup/models.py b/tests/lookup/models.py
--- a/tests/lookup/models.py
+++ b/tests/lookup/models.py
@@ -96,3 +96,15 @@ class Product(models.Model):
class Stock(models.Model):
product = models.ForeignKey(Product, models.CASCADE)
qty_available = models.DecimalField(max_digits=6, decimal_plac... | Prevent using __isnull lookup with non-boolean value.
Description
(last modified by Mariusz Felisiak)
__isnull should not allow for non-boolean values. Using truthy/falsey doesn't promote INNER JOIN to an OUTER JOIN but works fine for a simple queries. Using non-boolean values is undocumented and untested. IMO... | PR here: https://github.com/django/django/pull/11873
After the reconsideration I don't think that we should change this documented behavior (that is in Django from the very beginning). __isnull lookup expects boolean values in many places and IMO it would be confusing if we'll allow for truthy/falsy values, e.g. take... | 2019-10-11T18:19:39Z | 3.1 | ["test_isnull_non_boolean_value (lookup.tests.LookupTests)", "test_iterator (lookup.tests.LookupTests)"] | ["test_chain_date_time_lookups (lookup.tests.LookupTests)", "test_count (lookup.tests.LookupTests)", "test_custom_field_none_rhs (lookup.tests.LookupTests)", "Lookup.can_use_none_as_rhs=True allows None as a lookup value.", "test_error_messages (lookup.tests.LookupTests)", "test_escaping (lookup.tests.LookupTests)", "t... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-11742 | fee75d2aed4e58ada6567c464cfd22e89dc65f4a | diff --git a/django/db/models/fields/__init__.py b/django/db/models/fields/__init__.py
--- a/django/db/models/fields/__init__.py
+++ b/django/db/models/fields/__init__.py
@@ -257,6 +257,7 @@ def is_value(value, accept_promise=True):
)
]
+ choice_max_length = 0
# Expect [g... | diff --git a/tests/invalid_models_tests/test_ordinary_fields.py b/tests/invalid_models_tests/test_ordinary_fields.py
--- a/tests/invalid_models_tests/test_ordinary_fields.py
+++ b/tests/invalid_models_tests/test_ordinary_fields.py
@@ -304,6 +304,32 @@ class Model(models.Model):
self.assertEqual(Model._meta.g... | Add check to ensure max_length fits longest choice.
Description
There is currently no check to ensure that Field.max_length is large enough to fit the longest value in Field.choices.
This would be very helpful as often this mistake is not noticed until an attempt is made to save a record with those values that are to... | 2019-09-04T08:30:14Z | 3.0 | ["test_choices_in_max_length (invalid_models_tests.test_ordinary_fields.CharFieldTests)", "test_choices_named_group (invalid_models_tests.test_ordinary_fields.CharFieldTests)"] | ["test_non_nullable_blank (invalid_models_tests.test_ordinary_fields.GenericIPAddressFieldTests)", "test_forbidden_files_and_folders (invalid_models_tests.test_ordinary_fields.FilePathFieldTests)", "test_max_length_warning (invalid_models_tests.test_ordinary_fields.IntegerFieldTests)", "test_primary_key (invalid_models... | 419a78300f7cd27611196e1e464d50fd0385ff27 | |
django/django | django__django-11910 | d232fd76a85870daf345fd8f8d617fe7802ae194 | diff --git a/django/db/migrations/autodetector.py b/django/db/migrations/autodetector.py
--- a/django/db/migrations/autodetector.py
+++ b/django/db/migrations/autodetector.py
@@ -927,6 +927,10 @@ def generate_altered_fields(self):
if remote_field_name:
to_field_rename_key = rename_... | diff --git a/tests/migrations/test_autodetector.py b/tests/migrations/test_autodetector.py
--- a/tests/migrations/test_autodetector.py
+++ b/tests/migrations/test_autodetector.py
@@ -932,6 +932,30 @@ def test_rename_foreign_object_fields(self):
changes, 'app', 0, 1, model_name='bar', old_name='second', new... | # ForeignKey `to_field` Not Updated When Renaming PrimaryKey Fields
## Issue Description
When renaming a field that serves as a primary key using Django's migration system, foreign keys that explicitly reference this field via the `to_field` parameter continue to point to the old field name rather than updating to the... | Thanks for this ticket. It looks like a regression in dcdd219ee1e062dc6189f382e0298e0adf5d5ddf, because an AlterField operation wasn't generated in such cases before this change (and I don't think we need it). | 2019-10-14T01:56:49Z | 3.1 | ["test_rename_referenced_primary_key (migrations.test_autodetector.AutodetectorTests)"] | ["test_add_alter_order_with_respect_to (migrations.test_autodetector.AutodetectorTests)", "test_add_blank_textfield_and_charfield (migrations.test_autodetector.AutodetectorTests)", "Test change detection of new constraints.", "test_add_date_fields_with_auto_now_add_asking_for_default (migrations.test_autodetector.Autod... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-12286 | 979f61abd322507aafced9627702362e541ec34e | diff --git a/django/core/checks/translation.py b/django/core/checks/translation.py
--- a/django/core/checks/translation.py
+++ b/django/core/checks/translation.py
@@ -1,4 +1,5 @@
from django.conf import settings
+from django.utils.translation import get_supported_language_variant
from django.utils.translation.trans_r... | diff --git a/tests/check_framework/test_translation.py b/tests/check_framework/test_translation.py
--- a/tests/check_framework/test_translation.py
+++ b/tests/check_framework/test_translation.py
@@ -3,7 +3,7 @@
check_language_settings_consistent, check_setting_language_code,
check_setting_languages, check_set... | # Enhanced Problem Statement: Django translation.E004 Error with Valid Language Sublanguages
## Issue Description
Django's system check framework incorrectly raises `translation.E004` error when a sublanguage (e.g., "de-at") is specified in `LANGUAGE_CODE` setting, even though its base language (e.g., "de") is availab... | Thanks for this report. Regression in 4400d8296d268f5a8523cd02ddc33b12219b2535. | 2020-01-07T13:56:28Z | 3.1 | ["test_valid_variant_consistent_language_settings (check_framework.test_translation.TranslationCheckTests)"] | ["test_inconsistent_language_settings (check_framework.test_translation.TranslationCheckTests)", "test_invalid_language_code (check_framework.test_translation.TranslationCheckTests)", "test_invalid_languages (check_framework.test_translation.TranslationCheckTests)", "test_invalid_languages_bidi (check_framework.test_tr... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-12747 | c86201b6ed4f8256b0a0520c08aa674f623d4127 | diff --git a/django/db/models/deletion.py b/django/db/models/deletion.py
--- a/django/db/models/deletion.py
+++ b/django/db/models/deletion.py
@@ -408,7 +408,8 @@ def delete(self):
# fast deletes
for qs in self.fast_deletes:
count = qs._raw_delete(using=self.using)
- ... | diff --git a/tests/delete/tests.py b/tests/delete/tests.py
--- a/tests/delete/tests.py
+++ b/tests/delete/tests.py
@@ -522,11 +522,10 @@ def test_queryset_delete_returns_num_rows(self):
existed_objs = {
R._meta.label: R.objects.count(),
HiddenUser._meta.label: HiddenUser.objects.count... | # QuerySet.Delete: Inconsistent Results When Zero Objects Deleted
## Issue Description
The `QuerySet.delete()` method returns inconsistent results when no objects are deleted. This method returns a tuple `(total_count, model_counts)`, where `total_count` is the total number of deleted objects (including cascaded delet... | I guess we could adapt the code not to include any key if the count is zero in the second case. | 2020-04-18T16:41:40Z | 3.1 | ["test_fast_delete_empty_no_update_can_self_select (delete.tests.FastDeleteTests)", "test_model_delete_returns_num_rows (delete.tests.DeletionTests)", "test_queryset_delete_returns_num_rows (delete.tests.DeletionTests)"] | ["test_fast_delete_combined_relationships (delete.tests.FastDeleteTests)", "test_fast_delete_fk (delete.tests.FastDeleteTests)", "test_fast_delete_inheritance (delete.tests.FastDeleteTests)", "test_fast_delete_instance_set_pk_none (delete.tests.FastDeleteTests)", "test_fast_delete_joined_qs (delete.tests.FastDeleteTest... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-13768 | 965d2d95c630939b53eb60d9c169f5dfc77ee0c6 | diff --git a/django/dispatch/dispatcher.py b/django/dispatch/dispatcher.py
--- a/django/dispatch/dispatcher.py
+++ b/django/dispatch/dispatcher.py
@@ -1,3 +1,4 @@
+import logging
import threading
import warnings
import weakref
@@ -5,6 +6,8 @@
from django.utils.deprecation import RemovedInDjango40Warning
from djang... | diff --git a/tests/dispatch/tests.py b/tests/dispatch/tests.py
--- a/tests/dispatch/tests.py
+++ b/tests/dispatch/tests.py
@@ -165,13 +165,28 @@ def test_send_robust_fail(self):
def fails(val, **kwargs):
raise ValueError('this')
a_signal.connect(fails)
- result = a_signal.send_robu... | # Enhanced Problem Statement: Signal Exception Logging
## Issue Description
Django's `Signal.send_robust()` method silently catches exceptions raised in signal receivers without logging them, contrary to Django's usual practice of logging exceptions in similar situations (such as missing template variables). This crea... | I would like to work on this issue. PS. i am new to this django. so any advice would be appreciated | 2020-12-12T07:34:48Z | 3.2 | ["test_send_robust_fail (dispatch.tests.DispatcherTests)"] | ["test_receiver_signal_list (dispatch.tests.ReceiverTestCase)", "test_receiver_single_signal (dispatch.tests.ReceiverTestCase)", "test_cached_garbaged_collected (dispatch.tests.DispatcherTests)", "test_cannot_connect_no_kwargs (dispatch.tests.DispatcherTests)", "test_cannot_connect_non_callable (dispatch.tests.Dispatch... | 65dfb06a1ab56c238cc80f5e1c31f61210c4577d |
django/django | django__django-12708 | 447980e72ac01da1594dd3373a03ba40b7ee6f80 | diff --git a/django/db/backends/base/schema.py b/django/db/backends/base/schema.py
--- a/django/db/backends/base/schema.py
+++ b/django/db/backends/base/schema.py
@@ -393,7 +393,12 @@ def alter_index_together(self, model, old_index_together, new_index_together):
news = {tuple(fields) for fields in new_index_to... | diff --git a/tests/migrations/test_base.py b/tests/migrations/test_base.py
--- a/tests/migrations/test_base.py
+++ b/tests/migrations/test_base.py
@@ -62,7 +62,11 @@ def assertIndexExists(self, table, columns, value=True, using='default', index_t
any(
c["index"]
... | # Migration Crashes When Deleting index_together with Overlapping unique_together
## Issue Description
In Django 1.11.10, there's a critical issue when attempting to delete an `index_together` constraint that shares the same fields with a `unique_together` constraint. The migration system fails to distinguish between ... | Reproduced on master at 623139b5d1bd006eac78b375bcaf5948e695c3c6.
I haven't looked under the hood on this yet, but could it be related to the ordering of the operations generated for the mgiration? on first inspection it feels like this and #28862 could be caused by the same/similar underlying problem in how FieldRelat... | 2020-04-12T22:20:59Z | 3.1 | ["test_alter_index_together_remove_with_unique_together (migrations.test_operations.OperationTests)"] | ["test_references_model_mixin (migrations.test_operations.TestCreateModel)", "test_reference_field_by_through_fields (migrations.test_operations.FieldOperationTests)", "test_references_field_by_from_fields (migrations.test_operations.FieldOperationTests)", "test_references_field_by_name (migrations.test_operations.Fiel... | 0668164b4ac93a5be79f5b87fae83c657124d9ab |
django/django | django__django-13321 | 35b03788b0607c1f8d2b64e4fa9e1669b0907ea4 | diff --git a/django/contrib/sessions/backends/base.py b/django/contrib/sessions/backends/base.py
--- a/django/contrib/sessions/backends/base.py
+++ b/django/contrib/sessions/backends/base.py
@@ -121,6 +121,15 @@ def decode(self, session_data):
return signing.loads(session_data, salt=self.key_salt, serializ... | diff --git a/tests/sessions_tests/tests.py b/tests/sessions_tests/tests.py
--- a/tests/sessions_tests/tests.py
+++ b/tests/sessions_tests/tests.py
@@ -333,11 +333,16 @@ def test_default_hashing_algorith_legacy_decode(self):
self.assertEqual(self.session._legacy_decode(encoded), data)
def test_decode... | # Enhanced Problem Statement: Django Session Decoding Crash with Invalid Sessions
## Issue Description
After upgrading to Django 3.1, the application crashes when trying to process requests containing invalid or corrupted session data. The issue occurs specifically when browsing to any URL with Chrome browser (but not... | I tried to run clearsessions, but that didn't help. The only workaround was to delete all rows in the django_session table.
Thanks for this report, however I cannot reproduce this issue. Can you provide a sample project? Support for user sessions created by older versions of Django remains until Django 4.0. See similar... | 2020-08-18T10:43:52Z | 3.2 | ["test_clear (sessions_tests.tests.CookieSessionTests)", "test_custom_expiry_datetime (sessions_tests.tests.CookieSessionTests)", "test_custom_expiry_reset (sessions_tests.tests.CookieSessionTests)", "test_custom_expiry_seconds (sessions_tests.tests.CookieSessionTests)", "test_custom_expiry_timedelta (sessions_tests.te... | [] | 65dfb06a1ab56c238cc80f5e1c31f61210c4577d |
django/django | django__django-12908 | 49ae7ce50a874f8a04cd910882fb9571ff3a0d7a | diff --git a/django/db/models/query.py b/django/db/models/query.py
--- a/django/db/models/query.py
+++ b/django/db/models/query.py
@@ -1138,6 +1138,7 @@ def distinct(self, *field_names):
"""
Return a new QuerySet instance that will select only distinct results.
"""
+ self._not_support_... | diff --git a/tests/queries/test_qs_combinators.py b/tests/queries/test_qs_combinators.py
--- a/tests/queries/test_qs_combinators.py
+++ b/tests/queries/test_qs_combinators.py
@@ -272,6 +272,7 @@ def test_unsupported_operations_on_combined_qs(self):
'annotate',
'defer',
... | # Enhanced Problem Statement: DISTINCT ON Not Working with UNION Queryset
## Issue Description
When applying `.distinct()` with field arguments (e.g., `.distinct('name')`) on a queryset that is the result of a `.union()` operation on annotated querysets, the distinct operation is not properly applied to the combined r... | distinct() is not supported but doesn't raise an error yet. As per the documentation, "only LIMIT, OFFSET, COUNT(*), ORDER BY, and specifying columns (i.e. slicing, count(), order_by(), and values()/values_list()) are allowed on the resulting QuerySet.". Follow up to #27995. | 2020-05-13T11:36:48Z | 3.2 | ["test_unsupported_operations_on_combined_qs (queries.test_qs_combinators.QuerySetSetOperationTests)", "test_unsupported_ordering_slicing_raises_db_error (queries.test_qs_combinators.QuerySetSetOperationTests)"] | ["test_combining_multiple_models (queries.test_qs_combinators.QuerySetSetOperationTests)", "test_count_difference (queries.test_qs_combinators.QuerySetSetOperationTests)", "test_count_intersection (queries.test_qs_combinators.QuerySetSetOperationTests)", "test_count_union (queries.test_qs_combinators.QuerySetSetOperati... | 65dfb06a1ab56c238cc80f5e1c31f61210c4577d |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 4