per page, with , order by , clip by
Results of 1 - 10 of about 590 for Using (0.018 sec.)
メールを送信する — Django 6.1 ドキュメント 7687
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ックエンド lists the email backends that come with Django. The example above uses Django's SMTP email backend , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own ... Changed in Django 6.1: In earlier releases, Django defaulted to sending email through an SMTP server running on localhost, using the now-deprecated EMAIL_BACKEND and related settings. バージョン 6.1 で非推奨: Until Django 2028, if the MAILERS setting ... is not defined then the earlier behavior still applies: Django will default to using an SMTP server on localhost (but will issue deprecation warnings). Starting in Django 2028, attempts to send email without ...
https://man.mtool.work/django/6.1/topics/email.html
メールを送信する — Django 6.1 ドキュメント 7687
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » メールを送信する ¶ Django provides wrappers for Python's email and smtplib modules to simplify composing and sending email. Django's email framework ... ックエンド lists the email backends that come with Django. The example above uses Django's SMTP email backend , which sends using the standard SMTP protocol. This backend is useful for many production configurations, including SMTP servers in your own ... Changed in Django 6.1: In earlier releases, Django defaulted to sending email through an SMTP server running on localhost, using the now-deprecated EMAIL_BACKEND and related settings. バージョン 6.1 で非推奨: Until Django 2028, if the MAILERS setting ... is not defined then the earlier behavior still applies: Django will default to using an SMTP server on localhost (but will issue deprecation warnings). Starting in Django 2028, attempts to send email without ...
https://man.mtool.work/django/6.1/topics/email.html
複数のデータベース — Django 6.1 ドキュメント 7425
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 複数のデータベース ¶ ここでは、Djangoがサポートする複数データベースの扱いについて説明します。残りのDjangoのドキュメントの大部分は、あなたが一つのデー ... の時点でも、 QuerySet のデータベースを選択できます。指定したデータベースを使用する別の QuerySet を取得するには、 QuerySet の using() を呼び出します。 using() は引数を1つ取り、クエリを実行したいデータベースのエイリアスを指定します。例えば次のようにします ... : >>> # This will run on the 'default' database. >>> Author . objects . all () >>> # So will this. >>> Author . objects . using ( "default" ) >>> # This will run on the 'other' database. >>> Author . objects . using ( "other" ) save() のためのデータベ ... ースを選択する ¶ データを保存するデータベースを指定するには Model.save() に using キーワードを使用します。 例えば、 legacy_users データベースにオブジェクトを保存するには、次のようにします: >>> my_object . ...
https://man.mtool.work/django/6.1/topics/db/multi-db.html
複数のデータベース — Django 6.1 ドキュメント 7425
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 複数のデータベース ¶ ここでは、Djangoがサポートする複数データベースの扱いについて説明します。残りのDjangoのドキュメントの大部分は、あなたが一つのデー ... の時点でも、 QuerySet のデータベースを選択できます。指定したデータベースを使用する別の QuerySet を取得するには、 QuerySet の using() を呼び出します。 using() は引数を1つ取り、クエリを実行したいデータベースのエイリアスを指定します。例えば次のようにします ... : >>> # This will run on the 'default' database. >>> Author . objects . all () >>> # So will this. >>> Author . objects . using ( "default" ) >>> # This will run on the 'other' database. >>> Author . objects . using ( "other" ) save() のためのデータベ ... ースを選択する ¶ データを保存するデータベースを指定するには Model.save() に using キーワードを使用します。 例えば、 legacy_users データベースにオブジェクトを保存するには、次のようにします: >>> my_object . ...
https://man.mtool.work/django/6.1/topics/db/multi-db.html
Django 1.8 リリースノート — Django 6.1 ドキュメント 6812
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... ncat , and Substr . TestCase data setup ¶ TestCase has been refactored to allow for data initialization at the class level using transactions and savepoints. Database backends which do not support transactions, like MySQL with the MyISAM storage engin ... and one for each test. The class method TestCase.setUpTestData() adds the ability to set up test data at the class level. Using this technique can speed up the tests as compared to using setUp() . Fixture loading within TestCase is now performed once ... ates whether the user may access the site. Foreign key dropdowns now have buttons for changing or deleting related objects using a popup. django.contrib.admindocs ¶ reStructuredText is now parsed in model docstrings. django.contrib.auth ¶ 権限チェック ...
https://man.mtool.work/django/6.1/releases/1.8.html
Django 1.8 リリースノート — Django 6.1 ドキュメント 6685
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8 リリースノート ¶ April 1, 2015 Django 1.8 へようこそ! このリリースノートでは、 バージョン 1.8 の新機能 と、Django 1.7 以前からアップグレー ... ncat , and Substr . TestCase data setup ¶ TestCase has been refactored to allow for data initialization at the class level using transactions and savepoints. Database backends which do not support transactions, like MySQL with the MyISAM storage engin ... and one for each test. The class method TestCase.setUpTestData() adds the ability to set up test data at the class level. Using this technique can speed up the tests as compared to using setUp() . Fixture loading within TestCase is now performed once ... ates whether the user may access the site. Foreign key dropdowns now have buttons for changing or deleting related objects using a popup. django.contrib.admindocs ¶ reStructuredText is now parsed in model docstrings. django.contrib.auth ¶ 権限チェック ...
https://man.mtool.work/django/6.1/releases/1.8.html
Unit tests — Django 6.1 ドキュメント 6251
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... ases to use. To help you get started, Django provides and uses a sample settings module that uses the SQLite database. See Using another settings module to learn how to use a different settings module to run the tests with a different database. Having ... problems? See トラブルシューティング for some common issues. Running tests using tox ¶ Tox is a tool for running tests in different virtual environments. Django includes a basic tox.ini that automates so ... er than SQLite, however, you must create and provide your own test settings . For example, to run the tests on Python 3.12 using PostgreSQL: /  $ tox -e py312-postgres -- --settings = my_postgres_settings ...\> tox -e py312-postgres -- --settings=m ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Unit tests — Django 6.1 ドキュメント 6251
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Unit tests ¶ Django comes with a test suite of its own, in the tests directory of the code base. It's our policy to make sure all tests pass at all ... ases to use. To help you get started, Django provides and uses a sample settings module that uses the SQLite database. See Using another settings module to learn how to use a different settings module to run the tests with a different database. Having ... problems? See トラブルシューティング for some common issues. Running tests using tox ¶ Tox is a tool for running tests in different virtual environments. Django includes a basic tox.ini that automates so ... er than SQLite, however, you must create and provide your own test settings . For example, to run the tests on Python 3.12 using PostgreSQL: /  $ tox -e py312-postgres -- --settings = my_postgres_settings ...\> tox -e py312-postgres -- --settings=m ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/unit-tests...
Migrating email to mailers — Django 6.1 ドキュメント 5855
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... ed mail.mailers for obtaining configured email backend instances, replacing mail.get_connection() . A new using argument replaces the earlier connection in Django functions that send email. This guide provides details on migrating exi ... sting projects to the new mailers functionality. All Django projects that send email should: If using any third-party packages that send email, verify their compatibility with MAILERS before making other changes. Update emai ... Trying to access any of the deprecated EMAIL_* settings on django.conf.settings (e.g., checking settings.EMAIL_BACKEND or using settings.EMAIL_HOST_USER ). Calling mail.get_connection("path.to.EmailBackend") with a specific backend path. (Other argum ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
Migrating email to mailers — Django 6.1 ドキュメント 5638
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Migrating email to mailers ¶ Django 6.1 introduced the MAILERS setting, replacing EMAIL_BACKEND and several other EMAIL_* settings. It also introduc ... ed mail.mailers for obtaining configured email backend instances, replacing mail.get_connection() . A new using argument replaces the earlier connection in Django functions that send email. This guide provides details on migrating exi ... sting projects to the new mailers functionality. All Django projects that send email should: If using any third-party packages that send email, verify their compatibility with MAILERS before making other changes. Update emai ... Trying to access any of the deprecated EMAIL_* settings on django.conf.settings (e.g., checking settings.EMAIL_BACKEND or using settings.EMAIL_HOST_USER ). Calling mail.get_connection("path.to.EmailBackend") with a specific backend path. (Other argum ...
https://man.mtool.work/django/6.1/howto/mailers-migration.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT