Django-pgtrigger

Bug

- Fixed issues using ``pgtrigger.ignore`` with multiple databases [Wes Kendall, 557f0e1]

``pgtrigger.ignore`` now uses the connection of the database router
when ignoring triggers.

Feature

- Add ``pgtrigger.UpdateSearchVector`` to keep search vectors updated [Wes Kendall, 671e8be]

When using Django's full-text search, one can keep a
``SearchVectorField`` updated with the relevant document fields
by using ``pgtrigger.UpdateSearchVector``.

An example was added to the trigger cookbook.
- Added ``pgtrigger.constraints`` for runtime configuration of deferrable triggers [Wes Kendall, 4b77b7b]

``pgtrigger.constraints`` mimics Postgres's ``SET CONSTRAINTS`` statement, allowing one
to dynamically modify when a deferrable trigger runs.

Documentation was also added for deferrable triggers with an example in the cookbook.
- Added deferrable triggers [Wes Kendall, fe4f16e]

Triggers now have an optional ``timing`` argument. If set, triggers
will be created as "CONSTRAINT" triggers that can be deferred.

When ``timing`` is set to ``pgtrigger.Immediate``, the trigger will
run at the end of a statement. ``pgtrigger.Deferred`` will cause
the trigger to run at the end of the transaction.

Note that deferrable triggers must have both
``pgtrigger.After`` and ``pgtrigger.Row`` values set for the
``when`` and ``level`` attributes.

Bug

- Fixes ignoring triggers with nested transactions [Wes Kendall, d32113d]

``pgtrigger.ignore`` avoids injecting SQL when transactions are in a failed
state, allowing for one to use nested transactions while ignoring triggers.
- Fixed issue re-installing triggers with different conditions. [Wes Kendall, 68e29d2]

Triggers with conditions that change were not successfully
re-installed with ``pgtrigger.install``. Note that this only affects
legacy installation and not installation with the new migration system.

Feature

- Support proxy models on default many-to-many "through" relationships. [Wes Kendall, 4cb0f65]

Previously one had to use an unmanaged model to declare triggers on default
many-to-many "through" relationships. Users can now define a proxy model
on these instead.

Support for unmanaged models was dropped.

Api-Break

- Integration with Django's migration system. [Wes Kendall, 6916c14]

Triggers are fully integrated with Django's migration system, and they are no longer
installed at the end of migrations by default. Users instead need to run
``python manage.py makemigrations`` to make trigger migrations for their applications.

Triggers for models in third-party apps are declared with proxy models. Triggers
for default many-to-many "through" models are declared with unmanaged models.

For instructions on upgrading or preserving legacy behavior, see the frequently
asked questions of the docs.

Bug

- Fixed issues with proxy models and M2M "through" models. [Wes Kendall, 52aa81f]

Proxy models weren't creating migrations, and M2M "through" models are
handled by making an unmanaged model that points to the right DB table.

Feature

- Remove dependency on ``django-pgconnection``. [Wes Kendall, af0c908]

Users no longer have to wrap ``settings.DATABASES`` with
``django-pgconnection`` in order to use the ``pgtrigger.ignore``
function.

Trivial

- Updated with latest Django template, fixing doc builds [Wes Kendall, 4b175a4]

Bug

- Ignore non-postgres databases in global operations [Wes Kendall, a1aff5d]

Some operations, such as pruning triggers, would iterate over all databases
in a project, including non-postgres ones. This fix ignores non-postgres
databases.
- Fixes transaction leak when using ``pgtrigger.ignore()`` [Wes Kendall, 1501d7e]

``pgtrigger.ignore()`` would continue to ignore triggers until the end of the
transaction once the context manager exited. This is now fixed.
- Fixed more issues related to custom table names [Wes Kendall, a0e1f6d]

Fixes and test cases were added for custom table names that collide
with reserved words.
- Wrap table names to avoid SQL command conflicts [Zac Miller, 86ee983]

Prevents models/tables with names like Order from causing Syntax errors
and add PyCharm .idea/ folder to .gitignore

Feature

- Triggers can be specified in model Meta options [Wes Kendall, 5c1cfec]

Triggers can now be specified with the ``triggers`` attribute of a model's Meta
options. This still works alongside the old method of using ``pgtrigger.register``.