per page, with , order by , clip by
Results of 1 - 10 of about 130 for existing (0.004 sec.)
Django 1.0.1 リリースノート — Django 6.1 ドキュメント 10638
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0.1 リリースノート ¶ Django 1.0.1 へようこそ! This is the first "bugfix" release in the Django 1.0 series, improving the stability and perf ... databases, including pagination support for GIS QuerySets, more efficient slicing of results and improved introspection of existing databases. Several fixes for query support in the Django object-relational mapper, including repeated setting and resettin ... upports by default. And as always, a large number of improvements to Django's documentation, including both corrections to existing documents and expanded and new documentation. 目次 Django 1.0.1 リリースノート Fixes and improvements in Django 1.0.1 前の ... efault Multiple including forms literal passed join were codebase contains compatibility number Several ordering databases existing unique Fixed callable クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
https://man.mtool.work/django/6.1/releases/1.0.1.html
ロギング — Django 6.1 ドキュメント 10176
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ロギング ¶ 参考 ロギングの設定と利用 Django ロギング リファレンス Python プログラマは、素早く便利なデバッグツールとして、コード内で print() をよく使 ... ォルトでは、 LOGGING 設定は、以下のスキームを使って Django のデフォルトロギング設定 に統合されています。 LOGGING の disable_existing_loggers キーの値を True にすると、全てのデフォルトの設定が無効になります(キーが存在しない場合は dictConfig のデフォルトに ... なります)。このため、 'disable_existing_loggers': True を使う場合は注意してください。 True を設定する必要は殆どないでしょう。 disable_existing_loggers を False に ... ッセージをコンソールに出力するための最低限の設定がこちらです。 settings.py ¶ import os LOGGING = { "version" : 1 , "disable_existing_loggers" : False , "handlers" : { "console" : { "class" : "logging.StreamHandler" , }, }, "root" : { "handlers" : [ "conso ...
https://man.mtool.work/django/6.1/topics/logging.html
ロギング — Django 6.1 ドキュメント 9483
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ロギング ¶ 参考 ロギングの設定と利用 Django ロギング リファレンス Python プログラマは、素早く便利なデバッグツールとして、コード内で print() をよく使 ... ォルトでは、 LOGGING 設定は、以下のスキームを使って Django のデフォルトロギング設定 に統合されています。 LOGGING の disable_existing_loggers キーの値を True にすると、全てのデフォルトの設定が無効になります(キーが存在しない場合は dictConfig のデフォルトに ... なります)。このため、 'disable_existing_loggers': True を使う場合は注意してください。 True を設定する必要は殆どないでしょう。 disable_existing_loggers を False に ... ッセージをコンソールに出力するための最低限の設定がこちらです。 settings.py ¶ import os LOGGING = { "version" : 1 , "disable_existing_loggers" : False , "handlers" : { "console" : { "class" : "logging.StreamHandler" , }, }, "root" : { "handlers" : [ "conso ...
https://man.mtool.work/django/6.1/topics/logging.html
Django 3.0 リリースノート — Django 6.1 ドキュメント 8790
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0 リリースノート ¶ 2019年12月2日 Django 3.0 へようこそ! このリリースノートでは、 バージョン 3.0 の新機能 と、Django 2.2 以前からアップグレー ... ことによって、私たちは Django を完全な非同期処理が可能なフレームワークに作り変える旅を始めます。 This is in addition to our existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applicat ... dded BaseBackend class to ease customization of authentication backends. Added get_user_permissions() method to mirror the existing get_group_permissions() method. Added HTML autocomplete attribute to widgets of username, email, and password fields in dj ... ry key value equivalent to passing force_insert=True to model's save() . Attempts to use a new Model instance to update an existing row will result in an IntegrityError . In order to update an existing model for a specific primary key value, use the upda ...
https://man.mtool.work/django/6.1/releases/3.0.html
Django 3.0 リリースノート — Django 6.1 ドキュメント 8790
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0 リリースノート ¶ 2019年12月2日 Django 3.0 へようこそ! このリリースノートでは、 バージョン 3.0 の新機能 と、Django 2.2 以前からアップグレー ... ことによって、私たちは Django を完全な非同期処理が可能なフレームワークに作り変える旅を始めます。 This is in addition to our existing WSGI support. Django intends to support both for the foreseeable future. Async features will only be available to applicat ... dded BaseBackend class to ease customization of authentication backends. Added get_user_permissions() method to mirror the existing get_group_permissions() method. Added HTML autocomplete attribute to widgets of username, email, and password fields in dj ... ry key value equivalent to passing force_insert=True to model's save() . Attempts to use a new Model instance to update an existing row will result in an IntegrityError . In order to update an existing model for a specific primary key value, use the upda ...
https://man.mtool.work/django/6.1/releases/3.0.html
Django 6.1 release notes — Django 6.1 ドキュメント 8790
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... tch modes: FETCH_ONE , the default, fetches the missing field for the current instance only. This mode represents Django's existing behavior. FETCH_PEERS fetches a missing field for all instances that came from the same QuerySet . This mode works like an ... handle deletion logic entirely within the database, using the SQL ON DELETE clause. They are thus more efficient than the existing Python-level options, as Django does not need to load objects before deleting them. As a consequence, the DB_CASCADE optio ... signals. Mailers ¶ The new MAILERS setting supports configuring multiple email backends with different options, similar to existing mechanisms for CACHES , DATABASES , STORAGES , and TASKS : MAILERS = { "default" : { "BACKEND" : "django.core.mail.backend ...
https://man.mtool.work/django/6.1/releases/6.1.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8559
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4 リリースノート ¶ March 23, 2012 Django 1.4 へようこそ! These release notes cover the new features , as well as some backwards incompatibl ... C, use timezone-aware objects internally, and translate them to users' local timezones for display. If you're upgrading an existing project to Django 1.4, switching to the timezone aware mode may take some care: the new mode disallows some rather sloppy ... Time zone support is enabled by default in new projects created with startproject . If you want to use this feature in an existing project, read the migration guide . If you encounter problems, there's a helpful FAQ . Support for in-browser testing fram ... y just like with regular formsets. However, initial values only apply to extra forms, i.e. those which are not bound to an existing model instance. The sitemaps framework can now handle HTTPS links using the new Sitemap.protocol class attribute. A new dj ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.4 リリースノート — Django 6.1 ドキュメント 8559
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4 リリースノート ¶ March 23, 2012 Django 1.4 へようこそ! These release notes cover the new features , as well as some backwards incompatibl ... C, use timezone-aware objects internally, and translate them to users' local timezones for display. If you're upgrading an existing project to Django 1.4, switching to the timezone aware mode may take some care: the new mode disallows some rather sloppy ... Time zone support is enabled by default in new projects created with startproject . If you want to use this feature in an existing project, read the migration guide . If you encounter problems, there's a helpful FAQ . Support for in-browser testing fram ... y just like with regular formsets. However, initial values only apply to extra forms, i.e. those which are not bound to an existing model instance. The sitemaps framework can now handle HTTPS links using the new Sitemap.protocol class attribute. A new dj ...
https://man.mtool.work/django/6.1/releases/1.4.html
Django 1.0.1 リリースノート — Django 6.1 ドキュメント 8328
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.0.1 リリースノート ¶ Django 1.0.1 へようこそ! This is the first "bugfix" release in the Django 1.0 series, improving the stability and perf ... databases, including pagination support for GIS QuerySets, more efficient slicing of results and improved introspection of existing databases. Several fixes for query support in the Django object-relational mapper, including repeated setting and resettin ... upports by default. And as always, a large number of improvements to Django's documentation, including both corrections to existing documents and expanded and new documentation. 目次 Django 1.0.1 リリースノート Fixes and improvements in Django 1.0.1 前の ...
https://man.mtool.work/django/6.1/releases/1.0.1.html
Django 6.1 release notes — Django 6.1 ドキュメント 8097
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 6.1 release notes ¶ August 5, 2026 Welcome to Django 6.1! These release notes cover the new features , as well as some backwards incompatible ... tch modes: FETCH_ONE , the default, fetches the missing field for the current instance only. This mode represents Django's existing behavior. FETCH_PEERS fetches a missing field for all instances that came from the same QuerySet . This mode works like an ... handle deletion logic entirely within the database, using the SQL ON DELETE clause. They are thus more efficient than the existing Python-level options, as Django does not need to load objects before deleting them. As a consequence, the DB_CASCADE optio ... signals. Mailers ¶ The new MAILERS setting supports configuring multiple email backends with different options, similar to existing mechanisms for CACHES , DATABASES , STORAGES , and TASKS : MAILERS = { "default" : { "BACKEND" : "django.core.mail.backend ...
https://man.mtool.work/django/6.1/releases/6.1.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT