Imporve db archiving
I found a lot of problems with shadow tables.
1) Contributors that doesn't know about bp db-archiving (that was made in grizzly) are forgeting to update shadow tables in migrations examples:
https:/
https:/
and also one new patch (that is not in code)
https:/
So to avoid such kind of errors and improve a little bit situation we should make 2 things:
1) Add tests for checking that all tables have shadow table, and that columns in table and shadow table are equal
✓ 2) Add generic method in sqlalchemy.utils that creates shadow_table from table
Blueprint information
- Status:
- Complete
- Approver:
- Russell Bryant
- Priority:
- High
- Drafter:
- Boris Pavlovic
- Direction:
- Approved
- Assignee:
- Boris Pavlovic
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Boris Pavlovic
- Completed by
- Boris Pavlovic
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add sqlalchemy migration utils.check_
Addressed by: https:/
Add sqlalchemy migration utils.create_
Addressed by: https:/
Move get_table() from test_migrations to sqlalchemy.utils
Addressed by: https:/
Change db `deleted` column type utils
Addressed by: https:/
Sync shadow table for 175 and 176 migration
Addressed by: https:/
Remove copy past from 179 migration
Addressed by: https:/
Sync shadow table for 179 migration
Addressed by: https:/
Sync shadow table for 156 migration
Addressed by: https:/
Sync shadow table for 157 migration
Addressed by: https:/
Sync shadow table for 159 migration
Addressed by: https:/
Add db test that checks that shadow tables are up-to-date
Addressed by: https:/
Fix tests for sqlalchemy utils
Work Items
Dependency tree
* Blueprints in grey have been implemented.
