Closed
Bug 1008081
Opened 11 years ago
Closed 11 years ago
Remove "node" column from tokenserver "users" table
Categories
(Cloud Services Graveyard :: Server: Token, defect)
Cloud Services Graveyard
Server: Token
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Assigned: rfkelly)
References
Details
Attachments
(1 file)
|
2.15 KB,
patch
|
telliott
:
review+
|
Details | Diff | Splinter Review |
Once the fix from Bug 1002898 has been rolled out, we can do a second db migration to remove the no-longer-in-use "node" column from the "users" table.
| Assignee | ||
Comment 1•11 years ago
|
||
The previous migration is out in prod, we can now drop this column.
Attachment #8444909 -
Flags: review?(telliott)
Comment 2•11 years ago
|
||
Comment on attachment 8444909 [details] [diff] [review]
ts-remove-node-column.diff
Review of attachment 8444909 [details] [diff] [review]:
-----------------------------------------------------------------
Sweet. Stylistically, I'm a little nervous about removing the explicit table references from the join; it'll work, but it's a potential source of mysterious errors in the future if someone were to put back a node column. That's probably being excessively paranoid, though.
Attachment #8444909 -
Flags: review?(telliott) → review+
| Assignee | ||
Comment 3•11 years ago
|
||
> I'm a little nervous about removing the explicit table references from the join
Fair. I'll try putting them back in under an explicit alias and see how it affects overall readability.
| Assignee | ||
Comment 4•11 years ago
|
||
Committed with the explicit table reference restored:
https://github.com/mozilla-services/tokenserver/commit/3fe277d62a0d1ec58145dd7cba7a4ae903d82633
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•11 years ago
|
||
jbonacci, let's not verify this until we actually get the column dropped as part of the next tokenserver deployment.
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•