Resolve "Re-introduce data migrations" #1757
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!1757
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "137-re-introduce-data-migrations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #137
added 1 commit
Compare with previous version
unmarked as a Work In Progress
assigned to @nik
Nver import the User model directly. Please see the original migration code from BiscuIT or Django docs on what to do.
You need to do a few extra tricks to ensure the data access works in all configurations (for instance, use
usingt oselect the correct database). See the original migration code from BiscuIT.resolved all threads
changed this line in version 2 of the diff
changed this line in version 2 of the diff
added 1 commit
a07b3513- Re-introduce data migrations for admin user and school termCompare with previous version
This will fail if no SchoolTerm exists.
Actually, setting a schoolterm to current manually was only necessary because the migration was added after there already was one that created the term.
Now that we are recreating everything, just create the thing if none exists yet and forget about it.
What are these two migrations good for? ALso, why is the migration this is actually about (the data migration for the school term) not included ;)?
changed this line in version 3 of the diff
changed this line in version 3 of the diff
added 2 commits
7f5f8fab- 1 commit from branchmasterCompare with previous version
Because someone wrote a migration which had never worked and pushed it to master without testing ;).
No idea who „someone“ is :P…
added 1 commit
3ab70d86- Merge branch 'master' into 137-re-introduce-data-migrationsCompare with previous version
resolved all threads
added 3 commits
2d9cb6a7- 1 commit from branchmasterc683e6ba- Merge branch 'master' into 137-re-introduce-data-migrations6ab452cd- Fix migration.Compare with previous version
added 1 commit
c43ebd2a- FIx migration.Compare with previous version
mentioned in commit
f6625580c6merged