Remove Storm ORM dependency

Bug #397978 reported by Markus Korn
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
Fix Released
High
Mikkel Kamstrup Erlandsen
0.3
Fix Released
High
Mikkel Kamstrup Erlandsen

Bug Description

In the current state of zeitgeist we are using python-strom ORM as our database engine, but we are doing big parts of our queries by hand anyway. So we should drop strom as soon as possible.

Markus Korn (thekorn)
Changed in zeitgeist:
importance: Undecided → Medium
milestone: none → 0.2
Seif Lotfy (seif)
Changed in zeitgeist:
milestone: 0.2 → feature-freeze
summary: - Remove Storm ORM dependencie
+ Remove Storm ORM dependency
Seif Lotfy (seif)
Changed in zeitgeist:
assignee: nobody → Mikkel Kamstrup Erlandsen (kamstrup)
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I am working on a new engine called querymancer_engine.py in the branch lp:~kamstrup/zeitgeist/zeitgeist-querymancer-engine. Progress is good, but I have not completed the port away from Storm just yet (read:the engine is not in a working state).

Changed in zeitgeist:
importance: Medium → High
milestone: 0.3 → 0.2.1
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I just merged lp:~kamstrup/zeitgeist/zeitgeist-querymancer-engine. And is *almost* working. Storm is stil the default backend though. To test it out set the ZEITGEIST_ENGINE=querymancer environment variable.

Revision history for this message
Siegfried Gevatter (rainct) wrote :

This is now in the 0.2.1 branch and set to default. Could use some testing before release, or maybe additional unit tests.

Changed in zeitgeist:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.