Closed
Bug 799578
Opened 12 years ago
Closed 12 years ago
Update in-tree TBPL DB schema to match that in production
Categories
(Tree Management Graveyard :: TBPL, defect)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(8 files, 4 obsolete files)
6.25 KB,
text/plain
|
Details | |
4.65 KB,
patch
|
Details | Diff | Splinter Review | |
2.48 KB,
patch
|
Details | Diff | Splinter Review | |
4.22 KB,
patch
|
Details | Diff | Splinter Review | |
3.01 KB,
patch
|
Details | Diff | Splinter Review | |
3.32 KB,
patch
|
Details | Diff | Splinter Review | |
4.04 KB,
text/plain
|
Details | |
6.19 KB,
text/plain
|
Details |
In bug 798689 an index was added to runs_logs.content
At the least, this needs adding to:
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/schema.sql
...but I would also like to check whether there are any other not-checked-in changes in production.
Sheeri (or anyone else), could you possibly export the schema from production and paste in this bug at some point, for me then to update the in-tree copy.
Assignee | ||
Comment 1•12 years ago
|
||
Before I embark on bug 803009, I think it would be good to get the in-tree schema in sync with what's being used in production.
Sheeri, I don't suppose you could export the schema from tbpl production so I can compare with:
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/schema.sql
Cheers! :-)
Comment 2•12 years ago
|
||
sure, I can do that, changing this to confidential just in case (I have no clue if the code is open or what)
Group: mozilla-corporation-confidential
Comment 3•12 years ago
|
||
Assignee | ||
Comment 4•12 years ago
|
||
That's great, thank you :-)
(Unhiding, since we'll be syncing this with a public repo).
Group: mozilla-corporation-confidential
Assignee | ||
Comment 5•12 years ago
|
||
I reformatted the schema dump a bit so as to remove the most obvious false positives in the diff. Many of the remaining changes are also presumably non-issues (eg KEY index being a synonym of INDEX; PRIMARY KEY being listed on a separate line etc).
Assignee | ||
Updated•12 years ago
|
Attachment #675269 -
Attachment is patch: true
Assignee | ||
Comment 6•12 years ago
|
||
Assignee | ||
Comment 7•12 years ago
|
||
Updated diff of in-tree to production, with Part 1 patch applied and ignoring INDEX vs KEY differences.
Attachment #675269 -
Attachment is obsolete: true
Assignee | ||
Comment 8•12 years ago
|
||
...to match those in production.
Assignee | ||
Comment 9•12 years ago
|
||
...to match more typical style.
Assignee | ||
Comment 10•12 years ago
|
||
Diff with a number of false positives removed & patches parts 1-3 applied.
The main differences between production and in-tree are:
* Production has duplicate indexes on builders.buildername (!?).
* Production has some additional DEFAULT values specified in the runs table.
* Production's runs_notes index is on (`run_id`,`timestamp`) not just `run_id`.
* Production has an index on runs_logs.content (which we already knew).
Assignee | ||
Updated•12 years ago
|
Attachment #675283 -
Attachment is obsolete: true
Assignee | ||
Comment 11•12 years ago
|
||
Sheeri, sorry to bother you again - given the number of differences between the in-tree schema and production, I think it may be worth checking TBPL-dev too - so please may I have a dump of it as well?
Flags: needinfo?(scabral)
Assignee | ||
Comment 12•12 years ago
|
||
Assignee | ||
Comment 13•12 years ago
|
||
Assignee | ||
Comment 14•12 years ago
|
||
Attachment #675544 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Attachment #675325 -
Attachment is obsolete: true
Assignee | ||
Comment 15•12 years ago
|
||
With the attached patches, as far as I can tell, the in-tree schema is now identical to that in production (other than SQL style differences and s/KEY/INDEX/ etc).
Once they've landed & we have the tbpl-dev dump, I'll file separate bugs for the prod/dev DB changes required to fix up the problems found in comment 10 (eg the duplicate indices).
Assignee | ||
Comment 16•12 years ago
|
||
Assignee | ||
Comment 18•12 years ago
|
||
(In reply to Sheeri Cabral [:sheeri] from comment #17)
> Dev schema attached.
Thank you :-)
Differences between prod and dev:
* prod builders table has "KEY `buildername` (`buildername`(255))", dev does not
* prod runs_notes table has:
"KEY `runs_notes_run_id_idx` (`run_id`,`timestamp`)"
...whereas dev:
"KEY `runs_notes_run_id_idx` (`run_id`)"
Assignee | ||
Comment 19•12 years ago
|
||
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/3beaf22c67c4
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/16292ae0647d
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/a01985048f6d
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/2c3c34028518
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/cf6d5636562d
I'll file another bug for fixing the issues found in the prod schema (and getting dev in sync with prod).
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Webtools → Tree Management
Updated•10 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•