db migration version should be able to be specified in the CLI
Bug #1652708 reported by
Chaoyi Huang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tricircle |
Fix Released
|
Medium
|
Yipei Niu | ||
Bug Description
currently the version migrated to is fixed to 2 in cmd/manage.py, it's not correct. We should use the version specified in the CLI, if no target version is specified, then migrate the db to the latest version.
And at the same time, the command could be optimized like https:/
| summary: |
- db migration version should be able to be specified in the cli + db migration version should be able to be specified in the client |
| summary: |
- db migration version should be able to be specified in the client + db migration version should be able to be specified in the CLI |
Revision history for this message
| Chaoyi Huang (joehuang) wrote | #1 |
| Changed in tricircle: | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
| milestone: | none → pike-3 |
| assignee: | nobody → Yipei Niu (newypei) |
To post a comment you must log in.
The bug was fixed in https:/