6a3c8fe69c
Often we need to amend our schema, it is tempting to use drop_table, rename_column and drop_column to amned schema trouble though is that existing code that is running in production can depend on the existance of previous schema leading to application breaking until new code base is deployed. The commit enforces new rules to ensure we can never drop tables or columns in migrations and instead use Migration::ColumnDropper and Migration::TableDropper to defer drop the db objects |
||
|---|---|---|
| .. | ||
| 001_categories.rb | ||
| 002_groups.rb | ||
| 003_post_action_types.rb | ||
| 004_screened_ip_addresses.rb | ||
| 005_badge_types.rb | ||
| 006_badges.rb | ||
| 007_web_hook_event_types.rb | ||
| 009_users.rb | ||
| 500_lounge_category.rb | ||
| 501_meta_category.rb | ||
| 502_staff_category.rb | ||
| 600_themes.rb | ||
| 999_delayed.rb | ||
| 999_settings.rb | ||
| 999_topics.rb | ||