gabipetrovay/node-orientdb — comment on commit cc151b23a313cf4bce4746c9fc422b2a87b9fcce
File:  line 0
By ffissore:

I'm sorry to say that I'm quite new to orient. I'm working with it because I'm using neo4j on a ruby project and I'm willing to understand this one other graph db.
As you've already noticed, I wouldn't trust the DB_ prefix as something that conceptually belongs to the db.
The easiest path may be designing an API that's as close as possible to its java counterpart.

Speaking about the future, my wish is to use orient as a graph, so the API I would like to use has to do with nodes and relationships. Do you think it (as well as the document API) should go into this project? Or should it provide only the low level API?