We need to store the vulnerability model in db when job starts
Bug #932739 reported by
Muharem Hrnjadovic
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler | ||
Bug Description
Related to bug #809213 -- when a calculation starts we need to store the vulnerability model in the database first. All risk calculation logic shall access it from there using django model classes.
| Changed in openquake: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Muharem Hrnjadovic (al-maisan) |
| milestone: | none → 0.6.0 |
| tags: | added: 1model risk techdebt vulnerability |
| Changed in openquake: | |
| milestone: | 0.6.0 → 0.6.1 |
| Changed in openquake: | |
| assignee: | Muharem Hrnjadovic (al-maisan) → Lars Butler (lars-butler) |
| milestone: | 0.6.1 → 0.7.0 |
Revision history for this message
| Lars Butler (lars-butler) wrote | #1 |
| Changed in openquake: | |
| status: | Confirmed → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This has been fixed months ago.