Django 4.0.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem. LocMemCache". For example: CACHES0 码力 | 2248 页 | 7.90 MB | 1 年前3
Django 4.2.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3305 页 | 3.16 MB | 1 年前3- Django 4.1.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3240 页 | 3.13 MB | 1 年前3
- Django 4.0.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3184 页 | 3.14 MB | 1 年前3
- Django 3.1.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3094 页 | 3.03 MB | 1 年前3
- Django 3.2.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem. LocMemCache". For example: CACHES0 码力 | 2199 页 | 7.89 MB | 1 年前3
- Django 3.1.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends. locmem.LocMemCache". For example: CACHES0 码力 | 2053 页 | 6.92 MB | 1 年前3
- Django 3.2.x Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3121 页 | 3.08 MB | 1 年前3
- Django 5.1.2 Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core. cache.backends.locmem.LocMemCache". For example:0 码力 | 2923 页 | 9.62 MB | 1 年前3
- Django 5.1 Documentationdatabase query executions, and when exited, removes the wrapper. The wrapper is installed on the thread-local connection object. wrapper is a callable taking five arguments. It is called for every query the same database connection will be shared by two threads in parallel: the thread in which the live server is run and the thread in which the test case is run. It’s important to prevent simultaneous database running Memcached, consider the local-memory cache backend. This cache is per-process (see below) and thread-safe. To use it, set BACKEND to "django.core.cache.backends.locmem.LocMemCache". For example: CACHES0 码力 | 3513 页 | 3.17 MB | 1 年前3
共 30 条
- 1
- 2
- 3