... s custom SQL is to insert data into your database. If your custom SQL contains INSERT statements, those insertions will be performed every time your database is synchronized. This includes the synchronization of any test databases that are created when yo ... connection is closed. Until Django 1.3, transactions were only marked dirty when Django was aware of a modifying operation performed in them; that is, either some model was saved, some bulk update or delete was performed, or the user explicitly called tra ... nsaction.set_dirty() . In Django 1.3, a transaction is marked dirty when any database operation is performed. As a result of this change, you no longer need to set a transaction dirty explicitly when you execute raw SQL or use a da ... ... gation The support for time zones introduced in Django 1.4 didn't work well with QuerySet.dates() : aggregation was always performed in UTC. This limitation was lifted in Django 1.6. Use QuerySet.datetimes() to perform time zone aware aggregation on a Dat ... del.save() method now tries to directly UPDATE the database if the instance has a primary key value. Previously SELECT was performed to determine if UPDATE or INSERT were needed. The new algorithm needs only one query for updating an existing row while th ... presence of valid settings in commands that ask for it by using the BaseCommand.can_import_settings internal option is now performed independently from handling of the locale that should be active during the execution of the command. The latter can now be ... ... ration state changes in the Apps instance provided to the pre_migrate signal receivers to allow ContentType renaming to be performed on model rename ( #27100 ). Reallowed subclassing UserCreationForm without USERNAME_FIELD in Meta.fields ( #27111 ). Fixed ... ... n integer value, MySQL will first silently coerce the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur ... ... n integer value, MySQL will first silently coerce the strings to integers and return a result based on that. If a query is performed without first converting values to the appropriate type, this can produce unexpected results, similar to what would occur ... ... of files for changes. マイグレーション The new migrate --plan option prints the list of migration operations that will be performed. NoneType can now be serialized in migrations. You can now register custom serializers for migrations. モデル Added suppor ... ing specific fields on multiple model instances. Django no longer always starts a transaction when a single query is being performed, such as Model.save() , QuerySet.update() , and Model.delete() . This improves the performance of autocommit by reducing t ... ... request could reach this parsing through headers such as Accept or Content-Type , for instance via the content negotiation performed by HttpRequest.accepts() . The per-call length limit does not bound the combined size of repeated headers. The undocumente ... ... request could reach this parsing through headers such as Accept or Content-Type , for instance via the content negotiation performed by HttpRequest.accepts() . The per-call length limit does not bound the combined size of repeated headers. The undocumente ... ... s custom SQL is to insert data into your database. If your custom SQL contains INSERT statements, those insertions will be performed every time your database is synchronized. This includes the synchronization of any test databases that are created when yo ... ... request could reach this parsing through headers such as Accept or Content-Type , for instance via the content negotiation performed by HttpRequest.accepts() . The per-call length limit does not bound the combined size of repeated headers. The undocumente ... 2026年10月08日