... ックへ Django 1.8.12 リリースノート 関連キーワード MySQL SQLite リリースノート fixes several bugs バグ 修正 Fixed TimeField microseconds round tripping Restored conversion empty saving values GenericIPAddressField クイック検索 Last update: 2026年10月09日 « pr ... ... jango 1.8.12 リリースノート 関連キーワード Django MySQL SQLite リリースノート fixes several bugs バグ 修正 Fixed TimeField microseconds round tripping Restored conversion empty string null saving 関連するページ Django 1.10.2 リリースノート Django 1.11.8 リリ ... ... pleTestCase.assertRedirects() because Django 1.9 no longer converts redirects to absolute URIs ( #26428 ). Fixed TimeField microseconds round-tripping on MySQL and SQLite ( #26498 ). Prevented makemigrations from generating infinite migrations for a model fi ... ースノート Added support relative path client SimpleTestCase assertRedirects because longer converts absolute URIs TimeField microseconds round クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... pleTestCase.assertRedirects() because Django 1.9 no longer converts redirects to absolute URIs ( #26428 ). Fixed TimeField microseconds round-tripping on MySQL and SQLite ( #26498 ). Prevented makemigrations from generating infinite migrations for a model fi ... ... ations are deactivated ( #24569 ). Fixed squashmigrations command when using SeparateDatabaseAndState ( #24278 ). Stripped microseconds from datetime values when using an older version of the MySQLdb DB API driver as it does not support fractional seconds ( ... ... ations are deactivated ( #24569 ). Fixed squashmigrations command when using SeparateDatabaseAndState ( #24278 ). Stripped microseconds from datetime values when using an older version of the MySQLdb DB API driver as it does not support fractional seconds ( ... ... is stored in the native interval data type on PostgreSQL, as a INTERVAL DAY(9) TO SECOND(6) on Oracle, and as a bigint of microseconds on other backends. Date and time related arithmetic has also been improved on all backends. There is a corresponding form ... nsign() method now also accepts a datetime.timedelta object. データベースバックエンド ¶ The MySQL backend no longer strips microseconds from datetime values as MySQL 5.6.4 and up supports fractional seconds depending on the declaration of the datetime field ... ional precision greater than 0). New datetime database columns created with Django 1.8 and MySQL 5.6.4 and up will support microseconds. See the MySQL database notes for more details. The MySQL backend no longer creates explicit indexes for foreign keys when ... ... Django must emulate the other call style to allow your code to run. The per-call cost of this adaptation is small: tens of microseconds in the in-request ASGI path, where the running event loop is reused, and a few hundred microseconds in the cold-start path ... ... is stored in the native interval data type on PostgreSQL, as a INTERVAL DAY(9) TO SECOND(6) on Oracle, and as a bigint of microseconds on other backends. Date and time related arithmetic has also been improved on all backends. There is a corresponding form ... nsign() method now also accepts a datetime.timedelta object. データベースバックエンド ¶ The MySQL backend no longer strips microseconds from datetime values as MySQL 5.6.4 and up supports fractional seconds depending on the declaration of the datetime field ... ional precision greater than 0). New datetime database columns created with Django 1.8 and MySQL 5.6.4 and up will support microseconds. See the MySQL database notes for more details. The MySQL backend no longer creates explicit indexes for foreign keys when ... ... Django must emulate the other call style to allow your code to run. The per-call cost of this adaptation is small: tens of microseconds in the in-request ASGI path, where the running event loop is reused, and a few hundred microseconds in the cold-start path ... 2026年10月08日