Consolidate use of ORM

Registered by Lars Butler on 2011-08-03

As a prerequisite for implementing authentication/authorization, we need to consolidate our ORM code (which currently is part SQLAlchemy, part Django ORM) to a single framework (Django ORM).

Blueprint information

Status:
Complete
Approver:
John Tarter
Priority:
Undefined
Drafter:
Lars Butler
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Mattia Barbon on 2011-08-25
Completed by
Muharem Hrnjadovic on 2011-09-08

Related branches

Sprints

Whiteboard

In order to do away with the use of 2 different ORM frameworks (switching to Django ORM only), the following pieces of work need to be completed:

1) Convert existing SQLAlchemy models (openquake/db/alchemy/models.py) to Django models.
2) Update DB loader code (in openquake/utils/db/loader.py) to use Django ORM (and remove all use of SQLAlchemy)
3) Update DB serialization code for calculation artifacts to use Django ORM.
4) Complete the model code implementation to properly mirror the OpenQuake database. *

* This work may not be necessary right away. The first 2 conversion steps are much more important.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.