Django-pgclone

Latest version: v3.7.0

Safety actively analyzes 723625 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

2.2.0

Bug

- Restore command properly overrides storage location [Wes Kendall, 15acd90]

The restore command now properly passes through custom storage locations from the
command line.

2.1.0

Bug

- Allow "reversible" to proliferate through settings and configs. [Wes Kendall, bda7b69]

The ``pgclone restore`` command was setting ``reversible`` to
``False``, negating settings or configs that overrode it. This
has been fixed.

2.0.1

Trivial

- Update with latest Django template [Wes Kendall, c46d7e4]
- Fix ReadTheDocs builds [Wes Kendall, 7c74338]

2.0.0

Api-Break

- Upgrade configuration hierarchy, add multi-db support, and change dump key format [Wes Kendall, 5edeeb8]

``django-pgclone`` has ``settings.PGCLONE_CONFIGS`` to support re-usable command
options. Dump keys were changed to capture the config and also contain a configurable
database instance to better distinguish different databases.

Multi-database setups are fully supported.

Docs were revamped and overview all settings and configuration possibilities.

Instructions for migrating to version 2 are in the "Frequently Asked Questions" section of
the docs.

1.1.0

Feature

- Removed dependency on ``django-pgconnection`` [Wes Kendall, 5047031]

The routing functionality of ``django-pgconnection`` was replaced by
Django's built-in execution hooks.

Users no longer have to wrap ``settings.DATABASES`` with
``django-pgconnection``.

1.0.5

Trivial

- Updated with latest Django template [Wes Kendall, 5ab9ddd]

Page 4 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.