Convert existing SQLAlchemy models to Django models
Bug #820346 reported by
Lars Butler
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler | ||
Bug Description
The models defined in openquake/
This code should also be moved (perhaps to openquake/
Revision history for this message
| Lars Butler (lars-butler) wrote | #1 |
| Changed in openquake: | |
| milestone: | none → 0.4.3 |
| status: | New → Confirmed |
| description: | updated |
| description: | updated |
| Changed in openquake: | |
| status: | Confirmed → In Progress |
| Changed in openquake: | |
| assignee: | nobody → Lars Butler (lars-butler) |
| importance: | Undecided → Medium |
Revision history for this message
| Lars Butler (lars-butler) wrote | #2 |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
My plan is to keep the SQLAlchemy models in the code base for now. Once all of the dependent code has been refactored to use the Django models, the SQLAlchemy code can finally be removed.