Feature #655
Unify DB ORM
| Status: | Closed | Start date: | 21/12/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Jack Hong | % Done: | 100% |
|
| Category: | OMF Software | |||
| Target version: | OMF 5.4.1 |
Description
Don't know whether it is possible or simple to do this, basically we've many different ORM related gems across OMF modules, just a brief list from my observation:
datamapper
arel
activerecord
sequel
plus mysql and sqlite3 adapters, plus many dependent gems...
Maybe we could just choose one instead?
Related issues
History
Updated by Thierry Rakotoarivelo 4 months ago
- Target version changed from OMF 6.0 to OMF 5.4.1
From Max:
- delete Arel
Updated by Jack Hong 4 months ago
- Status changed from New to Resolved
- Assignee set to Jack Hong
As discussed, I removed Arel gem, and files that depend on Arel gem. Turns out ActiveRecord are only used in this files, so we can safely remove ActiveRecord gem too.
See commit
7407c627eaeefd892c3ad4719a42ca13c94d2850
for list of files have been removed.
Additionally, I removed oml-arel reference from oml-mstream class inside EC, and disabled 'addTab' and 'ms' method inside handlerCommands.rb.
Tested EC using hello_world_wired experiment (locally, connect to norbit):
omf-5.4 exec -e helloworldvm3_8 test:exp:tutorial:hello-world-wired -- --res1 omf.nicta.node30 --res2 omf.nicta.node32 --graph true
Result is here: http://norbit.npc.nicta.com.au:5054/result/dumpDatabase?expID=helloworldvm3_8