File: settings.rst

package info (click to toggle)
python-django-postgres-extra 2.0.9-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,096 kB
  • sloc: python: 9,057; makefile: 17; sh: 7; sql: 1
file content (40 lines) | stat: -rw-r--r-- 1,664 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
.. _settings:

Settings
========

.. _POSTGRES_EXTRA_DB_BACKEND_BASE:

* ``POSTGRES_EXTRA_DB_BACKEND_BASE``

   ``DATABASES[db_name]['ENGINE']`` must be set to ``"psqlextra.backend"``. If you're already using a custom back-end, set ``POSTGRES_EXTRA_DB_BACKEND_BASE`` to your custom back-end. This will instruct ``django-postgres-extra`` to wrap the back-end you specified.

   A good example of where this might be need is if you are using the PostGIS back-end: ``django.contrib.gis.db.backends.postgis``.

   **Default value**: ``django.db.backends.postgresql``

   .. warning::

      The custom back-end you specify must derive from the standard ``django.db.backends.postgresql``.

.. _POSTGRES_EXTRA_AUTO_EXTENSION_SET_UP:

* ``POSTGRES_EXTRA_AUTO_EXTENSION_SET_UP``

   You can stop ``django-postgres-extra`` from automatically trying to enable the ``hstore`` extension on your database. Enabling extensions using ``CREATE EXTENSION`` requires superuser permissions. Disable this behaviour if you are not connecting to your database server using a superuser.

   **Default value:** ``True``

   .. note::

      If set to ``False``, you must ensure that the ``hstore`` extension is enabled on your database manually. If not enabled, any ``hstore`` related functionality will not work.

.. _POSTGRES_EXTRA_ANNOTATE_SQL_:

* ``POSTGRES_EXTRA_ANNOTATE_SQL``

   If set to ``True``, will append a comment to all SQL queries with the path and line number that the query was made from.

   Format: ``/* <pid> <function name> <filename> <line number> */``

   This can be useful when debugging queries found in PostgreSQL's ``pg_stat_activity`` or in its query log.