Tested locally. Tests added.
Details
Diff Detail
- Repository
- rBLKR blockerbugs
- Lint
Lint Skipped - Unit
Unit Tests Skipped
alembic/versions/4df932caa9a9_add_needinfo_request.py | ||
---|---|---|
20 | When upgrading, needinfo won't be set to true and we lose information whether particular bug has needinfo. Do we want to do "update bug set needinfo to true where needinfo_requestee is not empty" in the migration script? Or are we ok with the current state? |
Functionality looks good to me. Per discussion on IRC, the migration has been tested with postgres
alembic/versions/4df932caa9a9_add_needinfo_request.py | ||
---|---|---|
20 | I think it depends on how much work that'd be. If it's quick, that'd be a nice-to-have but I don't think it'd be required. We'd be talking about only a few active bugs with needinfo set, so it wouldn't be horrible if we ended up needing to alter a few db records to make sure that the upgrade went smoothly and I'm not aware of any other folks using blockerbugs |
Bah, I didn't notice the change - phab still shows me as approved.
But, as long as this has been tested with postgres, looks good to me and no change on approved
When upgrading, needinfo won't be set to true and we lose information whether particular bug has needinfo. Do we want to do "update bug set needinfo to true where needinfo_requestee is not empty" in the migration script? Or are we ok with the current state?