XDump
XDump is an utility to make partial consistent dump and load it into the database.
The idea is to provide an ability to specify what to include in the dump via SQL queries. Responsibility for dump integrity lays on the user in this case.
Installation
XDump can be obtained with pip:
$ pip install xdump
Usage example
Making a dump (on production replica for example):
>>> EMPLOYEES_SQL = '''
WITH RECURSIVE employees_cte AS (
SELECT *
FROM recent_employees
UNION
SELECT E.*
FROM employees E
INNER JOIN employees_cte ON (employees_cte.manager_id = E.id)
), recent_employees AS (
SELECT *
FROM employees
ORDER BY id DESC
LIMIT 2
)
SELECT * FROM employees_cte
'''
>>> from xdump.postgresql import PostgreSQLBackend
>>> backend = PostgreSQLBackend(dbname='app_db', user='prod', password='pass', host='127.0.0.1', port='5432')
>>> backend.dump('/path/to/dump.zip', full_tables=['groups'], partial_tables={'employees': EMPLOYEES_SQL})
Load a dump on you local machine:
from xdump.postgresql import PostgreSQLBackend
>>> backend = PostgreSQLBackend(dbname='app_db', user='local', password='pass', host='127.0.0.1', port='5432')
>>> backend.load('/path/to/dump.zip')
RDBMS support
At the moment only the following are supported:
PostgreSQL
SQLite
Django support
Add xdump.extra.django to your INSTALLED_APPS settings:
INSTALLED_APPS = [
...,
'xdump.extra.django',
]
Add XDUMP to your project settings file. It should contain minimum 2 entries:
FULL_TABLES - a list of tables, that should be fully dumped.
PARTIAL_TABLES - a dictionary with table_name: select SQL
XDUMP = {
'FULL_TABLES': ['groups'],
'PARTIAL_TABLES': {'employees': 'SELECT * FROM employees WHERE id > 100'}
}
Optionally you could use a custom backend:
XDUMP = {
...,
'BACKEND': 'importable.string',
}
Run xdump command:
$ ./manage.py xdump dump.zip
Run xload command:
$ ./manage.py xload dump.zip
Possible options to both commands:
alias - allows you to choose database config from DATABASES, that is used during the execution;
backend - importable string, that leads to custom dump backend class.
The following make command could be useful to get a configured dump from production to your local machine:
sync-production:
ssh -t $(TARGET) "DJANGO_SETTINGS_MODULE=settings.production /path/to/manage.py xdump /tmp/dump.zip"
scp $(TARGET):/tmp/dump.zip ./dump.zip
ssh -t $(TARGET) "rm /tmp/dump.zip"
DJANGO_SETTINGS_MODULE=settings.local $(PYTHON) manage.py xload ./dump.zip
And usage is:
$ make sync-production TARGET=john@production.com PYTHON=/path/to/python/in/venv
Python support
XDump supports only Python 3.6 at the moment (but the supported versions list will be extended in the future).
Metadata
Release files for xdump 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| xdump-0.2.0.tar.gz | 10.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xdump-0.2.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 23.0 kB
Release files / xdump-0.2.0.tar.gz
| Download URL | xdump-0.2.0.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
037a1be9eda81780d3ef980e29e5f80b0874e84fe7dfc7b5ce12960ab124c525
|
|
BLAKE2b-256 checksum How to use checksums |
d556222b1d38a7993af5e5a67d45a3edaf81aab036c77d78055679c66f3f17a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / xdump-0.2.0-py2.py3-none-any.whl
| Download URL | xdump-0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
31f66a8bf39adba822de714d3f9d36c4150ac8838744e6b716b3c6587509b3fe
|
|
BLAKE2b-256 checksum How to use checksums |
ac67df1b74ad6c548cbcfaadc51f91d3754fa1ea4b18ab9aedf638853f181db6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |