#1433 closed Enhancement (fixed)
Consolidate sql and php migrations
| Reported by: | brettp | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Elgg 1.8.0 |
| Component: | Core | Version: | 1.6 |
| Severity: | minor | Keywords: | upgrade, migration |
| Cc: | brettp | Difficulty: | moderate |
Description
Currently database and PHP migrations are separate. Combining them into PHP-only upgrade gives you control over the exact order of the upgrades, something not currently possible. The benefits of flexibility and order control far outweigh the overhead of running SQL through the core engine.
Change History (7)
comment:1 Changed 3 years ago by brettp
- Type changed from unconfirmed defect to enhancement
comment:2 Changed 3 years ago by brettp
- Keywords upgrade, migration added
- Milestone changed from Elgg 1.7 to Elgg 1.8
- Priority changed from major to minor
comment:3 Changed 3 years ago by brettp
- Difficulty set to moderate
- Milestone changed from Elgg 1.8 to Elgg 1.9
comment:4 Changed 2 years ago by brettp
- Resolution set to fixed
- Status changed from new to closed
(In [svn:8277]) Fixes #1433, #2183. Upgrades are now tracked and will be run if needed regardless of version.
comment:5 Changed 2 years ago by brettp
Brought this in for 1.8 while fixing #2183. As of now SQL migrations are deprecated. Don't use them.
comment:6 Changed 2 years ago by brettp
(In [svn:8714]) Refs #1433. Restored db_upgrade() call during upgrades to fix issues for people upgrading from earlier versions of 1.7 than 2010062401. This is why we should follow deprecation policies, Brett........
comment:7 Changed 20 months ago by cash
- Milestone changed from Elgg 1.9 to Elgg 1.8.0
Note: See
TracTickets for help on using
tickets.
Moving this to 1.9. When dev of 1.9 starts, don't use any SQL migrations because that system will be gone.