Merge lp:~raj-abhilash1/mailman/alembic-fix into lp:mailman
Proposed by
Abhilash Raj
Status: | Merged |
---|---|
Merged at revision: | 7291 |
Proposed branch: | lp:~raj-abhilash1/mailman/alembic-fix |
Merge into: | lp:mailman |
Diff against target: |
74 lines (+30/-2) 2 files modified
src/mailman/database/alembic/env.py (+7/-2) src/mailman/docs/DATABASE.rst (+23/-0) |
To merge this branch: | bzr merge lp:~raj-abhilash1/mailman/alembic-fix |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mailman Coders | Pending | ||
Review via email: mp+246026@code.launchpad.net |
Description of the change
Fixed the autogeneration of migrations using alembic.
To post a comment you must log in.
Thanks for working on this. I think my problem is more basic. How do I run this - or maybe, *do* I even need to run this? For example, how would I create a migration for the pre-py3 branch merge to the current trunk, where a few columns changed from LargeBinary to Unicode?
Could you add some documentation on what needs to be done to make the migration work, say in src/mailman/ docs/DATABASE. rst? Or is everything so automatic that I don't need to do anything when the database model changes? (I doubt that. :)