Update instructions for database migration with additional steps that may be needed
Bug #1197570 reported by
Henry Gessau
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Henry Gessau |
Bug Description
These instructions
https:/
(and the README referred to therein) do not mention that backend-specific methods will be generated in the migration script, and that the developer must replace them with sa.* abstract methods.
Changed in neutron: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: low-hanging-fruit |
Changed in neutron: | |
assignee: | nobody → yelu (yeluaiesec) |
Changed in neutron: | |
assignee: | yelu (yeluaiesec) → Ann Kamyshnikova (akamyshnikova) |
Changed in neutron: | |
assignee: | Ann Kamyshnikova (akamyshnikova) → Akanksha (akanksha-aha) |
Changed in neutron: | |
status: | Triaged → In Progress |
Changed in neutron: | |
status: | In Progress → Confirmed |
tags: | added: db |
Changed in neutron: | |
milestone: | none → mitaka-1 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Does anyone use the automatic migration? I found it more difficult to use than just writing a migration script from scratch - since you have to go through and replace everything with sa.* methods - it may end up costing more time than it saves?