Closed
Bug 1178641
Opened 9 years ago
Closed 8 years ago
Move away from the multi database architecture & use the Django ORM
Categories
(Tree Management :: Treeherder, defect, P2)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Unassigned)
References
(Blocks 1 open bug)
Details
We have recently talked about moving to a more standard database architecture, with a unified database containing both reference and job data. This includes:
- create orm classes for every db table.
- adapt the api to use the new unified db schema.
- convert all the JobsModel methods into a orm counterpart, potentially switching to raw sql where necessary.
Reporter | ||
Comment 1•9 years ago
|
||
After some coding on this I still think it's a good idea but we need to tackle the problem in a more incremental way. I'll mark some bugs as blockers to keep track of the progress on this.
Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Summary: investigate what it would take to move away from the multi database architecture → Move away from the multi database architecture & use the Django ORM
Updated•9 years ago
|
Priority: -- → P2
Comment 3•8 years ago
|
||
Hi wlach, what is your current timeline for this?
Comment 4•8 years ago
|
||
(In reply to Armen Zambrano [:armenzg] (EDT/UTC-4) from comment #3)
> Hi wlach, what is your current timeline for this?
I am hoping to have this mostly finished (pending reviews) within ~1 week. The largest piece of work is bug 1306674.
Comment 5•8 years ago
|
||
treeherder no longer uses datasource in any way \o/
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•