... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... d results, similar to what would occur if the query itself had been manipulated. Django's model field classes are aware of their own types and most such classes perform explicit conversion of query arguments to the correct database-level type before q ... uerying. However, three model field classes did not correctly convert their arguments: FilePathField GenericIPAddressField IPAddressField These three fields have been updated to convert their argume ... correct types before querying. Additionally, developers of custom model fields are now warned via documentation to ensure their custom field classes will perform appropriate type conversions, and users of the raw() and extra() query methods -- which ... ... n you have multiple ManyToManyField s on different models that have the same field name, point to the same model, and have their reverse relations disabled ( #25545 ). Allowed filtering over a RawSQL annotation ( #25506 ). Made the Concat database fun ... ED_APPS setting ( #25510 ). This regression appeared in 1.8.5 as a side effect of fixing #24704 . Made deferred models use their proxied model's _meta.apps for caching and retrieval ( #25563 ). This prevents any models generated in data migrations usi ... ノート 次のトピックへ Django 1.8.5 リリースノート 関連キーワード Fixed regression crash model models Allowed SQLite database their Made invalid migrations allowed リリースノート November adds official support fixes several bugs バグ 修正 causing ModelCh ... ... uth no longer strip trailing and leading whitespace from the password fields ( #26334 ). The change requires users who set their password to something with such whitespace after a site updated to Django 1.9 to reset their password. It provides backwar ... ngo 1.9.4 リリースノート 関連キーワード Fixed crash password regression バグ 修正 SQLite values trailing whitespace fields their something after caused ForeignKey primary model リリースノート April Made MultiPartParser ignore filenames normalize クイッ ... ... uld affect only a small number of Django users, as most operating-system vendors today are shipping Python 2.7 or newer as their default version. If you're still using Python 2.6, however, you'll need to stick to Django 1.6 until you can upgrade your ... esent the model changes and which can be run on any development, staging or production database. Migrations are covered in their own documentation , but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't worry - ... ments thus far include: Applications can run code at startup, before Django does anything else, with the ready() method of their configuration. Application labels are assigned correctly to models even when they're defined outside of models.py . You do ... ... n you have multiple ManyToManyField s on different models that have the same field name, point to the same model, and have their reverse relations disabled ( #25545 ). Allowed filtering over a RawSQL annotation ( #25506 ). Made the Concat database fun ... ED_APPS setting ( #25510 ). This regression appeared in 1.8.5 as a side effect of fixing #24704 . Made deferred models use their proxied model's _meta.apps for caching and retrieval ( #25563 ). This prevents any models generated in data migrations usi ... ngo 1.8.5 リリースノート 関連キーワード Fixed Django regression name crash model models Allowed SQLite test database field their Made invalid migrations allowed リリースノート November adds 関連するページ Django 1.7.1 リリースノート Django 3.2.9 リリー ... 2026年10月08日