Liquibase migrations for Django
License: BSD
Documentation: https://liquimigrate.readthedocs.org.
History
0.5.2 (2015-10-22)
added management to MANIFEST.in
0.5.1 (2015-10-22)
handle liquibase return codes as an exception
0.5.0 (2015-08-06)
add documentation and better package layout
0.4.1 (2015-08-06)
fix for disabling signals
add possiblity to disable emitting pre- and postmigrate signals
add example project configured with liquibase migrations
0.4.0 (2014-09-28)
more detailed messages in makemigrations and squashmigrations commands
Django 1.7+ compatibility + wrapped migration commands
0.3.0 (2014-02-17)
Update README.rst
removed version from __init__
Update README.rst
back to previous versioning scheme
cleaned up settings header
Changed Makefile:pypi to not use iw.dist
Update README.rst
possibility to change liquibase jar and connectors via settings
db name, host, port were overriden by defaults
0.2.8 (2012-02-28)
Updated documentation about new LIQUIMIGRATE_CHANGELOG_FILES directive Renamed README.txt to README.rst & included into MANIFEST.in Print additional info only in –verbosity 1 model Minor changes for PEP8
full multidb support
0.2.7 (2011-06-01)
emit post_sync signal, call loaddata and initial_data
support for singledb django versions
fixed driver option
0.2.6 (2011-05-20)
accepting –driver option from command line
0.2.5 (2011-05-18)
Better README.txt - link to liquibase
0.2.4 (2011-05-17)
FIXED: project path
0.2.3 (2011-05-17)
Updated README.txt about mysql driver & about BSD license
0.2.2 (2011-05-17)
ADDED: pass other args as liquibase args
0.2.1 (2011-05-17)
FIXED: too small tuple when using not supported db driver
0.2.0 (2011-04-29)
ADDED: mysql connector
0.1.2 (2011-04-28)
ADDED: custom syncdb command
ADDED: ensure command was given & more README.txt
FIXED: run cmdline than just print them ;)
FIXED: missing vendor in egg
0.1.1 (2011-04-28)
REMOVED: old dependencies/namespaces
0.1.0 (2011-04-28)
Metadata
Release files for liquimigrate 0.6.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 | Provenance | Actions |
|---|---|---|---|---|
| liquimigrate-0.6.0.tar.gz | 3.0 MB | Without provenance | Details for liquimigrate-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liquimigrate-0.6.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for liquimigrate-0.6.0-py2.py3-none-any.whl |
Total release size: 6.0 MB
Release files / liquimigrate-0.6.0.tar.gz
| Download URL | liquimigrate-0.6.0.tar.gz |
|---|---|
| Size | 3.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5399b585b6f525a846c44e8d46f221762e4694c7b41561e1023af25a241af874
|
|
BLAKE2b-256 checksum How to use checksums |
762329d5e9b63a049638d069ee55baa005bd8e157ac92fc7b5c6fa020b7d23d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / liquimigrate-0.6.0-py2.py3-none-any.whl
| Download URL | liquimigrate-0.6.0-py2.py3-none-any.whl |
|---|---|
| Size | 3.0 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
de9986b64a46b8db83759e326f3c2115c859a04b396c4b51dc1a8ef9d1d281a6
|
|
BLAKE2b-256 checksum How to use checksums |
15dc917226f0e2fda2173f6736caf9c40f3548f17c59ff1dc0eaa4a1b1ce6234
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for liquimigrate 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.