... upport transactions, or when using a TransactionTestCase, data that has been inserted using custom SQL will not be visible during the testing process. Unfortunately, there was no way to rectify this problem without introducing a backwards incompatibili ... ed initial data in an uncertain state, Django now enforces the policy that data inserted by custom SQL will not be visible during testing. This change only affects the testing process. You can still use custom SQL to load data into your production data ... base as part of the syncdb process. If you require data to exist during test conditions, you should either insert it using test fixtures , or using the setUp() method of your test case. ModelAdm ... ... se table name quoting regression in 1.7.2 ( #24605 ). The loss of null / not null column properties during field alteration of MySQL databases ( #24595 ). 前のトピックへ Django 1.7.9 リリースノート 次のトピックへ Django 1.7.7 リリ ... リリースノート fixes Database introspection SQLite released April database table quoting regression loss column properties during alteration MySQL databases クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... se table name quoting regression in 1.7.2 ( #24605 ). The loss of null / not null column properties during field alteration of MySQL databases ( #24595 ). 前のトピックへ Django 1.7.9 リリースノート 次のトピックへ Django 1.7.7 リリ ... ースノート fixes Database introspection SQLite released April database table name quoting regression loss column properties during field alteration 関連するページ Django 1.8.13 リリースノート Django 1.8.6 リリースノート Django 2.0.1 リリースノート Djang ... ... upport transactions, or when using a TransactionTestCase, data that has been inserted using custom SQL will not be visible during the testing process. Unfortunately, there was no way to rectify this problem without introducing a backwards incompatibili ... ed initial data in an uncertain state, Django now enforces the policy that data inserted by custom SQL will not be visible during testing. This change only affects the testing process. You can still use custom SQL to load data into your production data ... base as part of the syncdb process. If you require data to exist during test conditions, you should either insert it using test fixtures , or using the setUp() method of your test case. ModelAdm ... ... option enabled. Screenshots will be saved to the tests/screenshots/ directory. To define when screenshots should be taken during a selenium test, the test class must use the @django.test.selenium.screenshot_cases decorator with a list of supported scr ... ppear as not covered when run on Ubuntu. Coverage doesn't equal quality: A line being "covered" only means it was executed during tests. It doesn't guarantee the line is well-tested or that all edge cases are handled. During review, assess test quality ... runtests.py basic --reverse ...\> runtests.py basic --shuffle ...\> runtests.py basic --reverse Seeing the SQL queries run during a test ¶ If you wish to examine the SQL being run in failing tests, you can turn on SQL logging using the --debug-sql opti ... ... option enabled. Screenshots will be saved to the tests/screenshots/ directory. To define when screenshots should be taken during a selenium test, the test class must use the @django.test.selenium.screenshot_cases decorator with a list of supported scr ... ppear as not covered when run on Ubuntu. Coverage doesn't equal quality: A line being "covered" only means it was executed during tests. It doesn't guarantee the line is well-tested or that all edge cases are handled. During review, assess test quality ... runtests.py basic --reverse ...\> runtests.py basic --shuffle ...\> runtests.py basic --reverse Seeing the SQL queries run during a test ¶ If you wish to examine the SQL being run in failing tests, you can turn on SQL logging using the --debug-sql opti ... ... vice attack via certain inputs with a large number of unmatched HTML end tags, which could cause quadratic time complexity during HTML parsing. This issue has severity "moderate" according to the Django security policy . CVE-2026-1287: Potential SQL in ... dset> aligned horizontally ( #36788 ). Fixed a regression in Django 6.0 where auto_now_add field values were not populated during INSERT operations, due to incorrect parameters passed to field.pre_save() ( #36847 ). 目次 Django 6.0.2 release notes CVE- ... ... vice attack via certain inputs with a large number of unmatched HTML end tags, which could cause quadratic time complexity during HTML parsing. This issue has severity "moderate" according to the Django security policy . CVE-2026-1287: Potential SQL in ... dset> aligned horizontally ( #36788 ). Fixed a regression in Django 6.0 where auto_now_add field values were not populated during INSERT operations, due to incorrect parameters passed to field.pre_save() ( #36847 ). 目次 Django 6.0.2 release notes CVE- ... ... that appears in ABSOLUTE_URL_OVERRIDES but doesn't define get_absolute_url() . Avoided masking some ImportError exceptions during application loading ( #22920 ). Empty index_together or unique_together model options no longer results in infinite migrat ... ta and indexes will be created for apps with migrations ( #23537 ). Coerced the related_name model field option to Unicode during migration generation to generate migrations that work with both Python 2 and 3 ( #23455 ). Fixed MigrationWriter to handle ... ... that appears in ABSOLUTE_URL_OVERRIDES but doesn't define get_absolute_url() . Avoided masking some ImportError exceptions during application loading ( #22920 ). Empty index_together or unique_together model options no longer results in infinite migrat ... ta and indexes will be created for apps with migrations ( #23537 ). Coerced the related_name model field option to Unicode during migration generation to generate migrations that work with both Python 2 and 3 ( #23455 ). Fixed MigrationWriter to handle ... 2026年10月08日