mo/mitlist
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: mo:8a98aee6c1c82102f43e90408829bccdc0c31596
Branches Tags
mo:ph4
mo:prod
mo:main
...
compare: mo:463cfe070cc4e754eb7f4151b8ed7b49a3290503
Branches Tags
mo:prod
mo:ph4
mo:main

2 Commits
8a98aee6c1 ... 463cfe070c

Author SHA1 Message Date
mo
463cfe070c Merge pull request 'refactor: Clarify access to revision strings in migration function by referencing Script object within RevisionStep' (#34) from ph4 into prod 
Reviewed-on: #34
 2025-06-01 18:09:45 +02:00
mohamad
02ab812ef0 refactor: Clarify access to revision strings in migration function by referencing Script object within RevisionStep
All checks were successful
Deploy to Production, build images and push to Gitea Registry / build_and_push (pull_request) Successful in 1m19s
Details
2025-06-01 18:09:31 +02:00
1 changed files with 2 additions and 2 deletions
Show Stats Expand all files Collapse all files

4
be/alembic/migrations.py
View File

@ -23,8 +23,8 @@ def _get_migration_fn(script_directory, current_rev):
# Get all upgrade steps from current revision to head
revisions = script_directory._upgrade_revs("head", current_rev)
for revision_step in revisions:
# Access the revision string from the RevisionStep object
script = script_directory.get_revision(revision_step.revision)
# Access the revision string from the Script object, which is within the RevisionStep object
script = script_directory.get_revision(revision_step.revision.revision)
script.module.upgrade(context)
return migration_fn