charettes / django-syzygy

97%

master: 97%

LAST BUILD ON BRANCH foreign-key-callable-default

branch: foreign-key-callable-default

CHANGE BRANCH

x

Reset

• foreign-key-callable-default
• 0.1.0a10
• 0.1.0a11
• 1.0.0
• 1.0.1
• 1.1.0
• 1.2.0
• 1.2.1
• add-field
• aliased-rename
• alter-null-to-not-null
• ambiguous-message-hint
• autodetector-split-phases
• avoid__class__swap
• coverage-increase
• deconstruct-tweaks
• django-5.2
• django-50
• django-db_default-shims
• elidable-removal
• empty-dirs-check
• incremental-fixes
• interactive-ambiguous-choices
• makemigrations-merge-crash
• many-to-many-addition
• many-to-many-field-removal
• master
• migrate-quorum
• mypy-ci
• mysql
• nullable-tweaks
• operation-split
• partition-plan-reorder
• postgres-13
• pre-remove-field-default
• pre-remove-field-op
• pre-remove-migration-name-fragment
• publish
• quorum-tweaks
• remove-pre_migrate-hack
• rename-ambiguous
• rename-issues
• severed-quorum
• stage-deploy
• stage-override-fallback
• tests-postgresql
• third-party-settings-visibility
• upgrade-deps

Build # 14609038341

Build Type

Pull #61

github

Committed by charettes

Commit Message

Fix #60 -- Adjust pre-AddField(db_default) for ForeignKey with callable defaults.

ForeignKey.get_default() cannot be safely called on instances that are not
bound to a model yet; this will have to be adjusted if Django's schema editor
is ever adjusted to operate from model states.

Thanks @jzmiller1 for the report.

Pull Request Pull Request #61: Fix #60 -- Adjust pre-AddField(db_default) for ForeignKey with callable defaults.

Run Details

269 of 288 branches covered (93.4%)

Branch coverage included in aggregate %.

8 of 8 new or added lines in 1 file covered. (100.0%)

718 of 732 relevant lines covered (98.09%)

4.72 hits per line