- changed
ADD COLUMN DEFAULT NULL
to safe operation for code default - changed
ADD COLUMN DEFAULT NOT NULL
to safe operation fordb_default
in django 5.0+ - added
ZERO_DOWNTIME_MIGRATIONS_KEEP_DEFAULT
settings and changedADD COLUMN DEFAULT NOT NULL
with this settings to safe operation for django<5.0 - added
ZERO_DOWNTIME_MIGRATIONS_EXPLICIT_CONSTRAINTS_DROP
settings and added dropping constraints and indexes before drop column or table - fixed sqlmigrate in idempotent mode
- fixed creation unique constraint with include parameter
- fixed idempotent mode tests
- updated unsafe migrations links to documentation
- updated patched code to latest django version
- updated test image to ubuntu 24.04
- improved README
- added idempotent mode and
ZERO_DOWNTIME_MIGRATIONS_IDEMPOTENT_SQL
setting - fixed django 3.2 degradation with missing
skip_default_on_alter
method - improved readme
- updated release github action
- fixed deferred sql errors
- added django 5.0 support
- added python 3.12 support
- added postgres 16 support
- drop postgres 11 support
- drop
ZERO_DOWNTIME_MIGRATIONS_USE_NOT_NULL
setting - marked
migrate_isnotnull_check_constraints
command deprecated
- added django 4.2 support
- marked django 3.2 support deprecated
- marked django 4.0 support deprecated
- marked django 4.1 support deprecated
- marked postgres 11 support deprecated
- drop postgres 10 support
- updated test docker image to ubuntu 22.04
- added
serial
andinteger
,bigserial
andbigint
,smallserial
andsmallint
, same types changes as safe migrations - fixed
AutoField
type changing and concurrent insertions issue fordjango<4.1
- added sequence dropping and creation timeouts as they can be used with
CASCADE
keyword and affect other tables - added django 4.1 support
- added python 3.11 support
- added postgres 15 support
- marked postgres 10 support deprecated
- drop django 2.2 support
- drop django 3.0 support
- drop django 3.1 support
- drop postgres 9.5 support
- drop postgres 9.6 support
- add github actions checks for pull requests
- fixed rename model with keeping
db_table
raisesALTER_TABLE_RENAME
error #26 - added django 3.2 support
- added django 4.0 support
- added python 3.9 support
- added python 3.10 support
- added postgres 14 support
- marked django 2.2 support deprecated
- marked django 3.0 support deprecated
- marked django 3.1 support deprecated
- marked python 3.6 support deprecated
- marked python 3.7 support deprecated
- marked postgres 9.5 support deprecated
- marked postgres 9.6 support deprecated
- move to github actions for testing
- added django 3.1 support
- added postgres 13 support
- drop python 3.5 support
- updated test environment
- fixed decimal to float migration error
- fixed django 3.0.2+ tests
- added django 3.0 support
- added concurrently index creation and removal operations
- added exclude constraint support as unsafe operation
- drop postgres 9.4 support
- drop django 2.0 support
- drop django 2.1 support
- drop deprecated
django_zero_downtime_migrations_postgres_backend
module
- added python 3.8 support
- added postgres specific indexes support
- improved tests clearness
- fixed regexp escaping warning for management command
- fixed style check
- improved README
- marked python 3.5 support deprecated
- marked postgres 9.4 support deprecated
- marked django 2.0 support deprecated
- marked django 2.1 support deprecated
- marked
ZERO_DOWNTIME_MIGRATIONS_USE_NOT_NULL
option deprecated for postgres 12+ - added management command for migration to real
NOT NULL
fromCHECK IS NOT NULL
constraint - added integration tests for pg 12, pg 11 root, pg 11 compatible not null constraint, pg 11 standard not null constraint and pg 10, 9.6, 9.5, 9.4, postgis databases
- fixed compatible check not null constraint deletion and creation via pg_attribute bugs
- minimized side affect with deferred sql execution between operations in one migration module
- added postgres 12 safe
NOT NULL
constraint creation - added safe
NOT NULL
constraint creation for extra permissions forpg_catalog.pg_attribute
withZERO_DOWNTIME_MIGRATIONS_USE_NOT_NULL=USE_PG_ATTRIBUTE_UPDATE_FOR_SUPERUSER
option enabled - marked
AddField
withnull=False
parameter and compatibleCHECK IS NOT NULL
constraint option as unsafe operation and avoidZERO_DOWNTIME_MIGRATIONS_USE_NOT_NULL
value in this case - added version to package
- fixed pypi README images links
- improved README
- extracted zero-downtime-schema to mixin to allow use this logic with other backends
- moved module from
django_zero_downtime_migrations_postgres_backend
todjango_zero_downtime_migrations.backends.postgres
- marked
django_zero_downtime_migrations_postgres_backend
module as deprecated - added postgis backend support
- improved README
- changed defaults for
ZERO_DOWNTIME_MIGRATIONS_LOCK_TIMEOUT
andZERO_DOWNTIME_MIGRATIONS_STATEMENT_TIMEOUT
from0ms
toNone
to get same with default django behavior that respect default postgres timeouts - added updates to documentations with options defaults
- added updates to documentations with best options usage
- fixed adding nullable field with default had no error and warning issue
- added links to documentation with issue describing and safe alternatives usage for errors and warnings
- added updates to documentations with type casting workarounds
- added django 2.2 support with
Meta.indexes
andMeta.constraints
attributes - fixed python deprecation warnings for regexp
- removed unused
TimeoutException
- improved README and PYPI description
- added option that allow disable
statement_timeout
for long operations like index creation on constraint validation when statement_timeout set globally
- added long description content type
- replaced default sql queries with more safe
- added options for
statement_timeout
andlock_timeout
- added option for
NOT NULL
constraint behaviour - added option for unsafe operation restriction