search

1602 / jugglingdb

Multi-database ORM for nodejs: redis, mongodb, mysql, sqlite3, postgresql, arango, in-memory...
http://1602.github.io/jugglingdb/
2.05k stars 241 forks source link

Support for OrientDB #279

Open kesavkolla opened 11 years ago

kesavkolla commented 11 years ago

Is it easy to write an adapter for OrientDB?

anatoliychakkaev commented 11 years ago

Absolutely.

On Wed, May 8, 2013 at 9:25 AM, kesavkolla notifications@github.com wrote:

Is it easy to write an adapter for OrientDB?

Reply to this email directly or view it on GitHub: https://github.com/1602/jugglingdb/issues/279

kesavkolla commented 11 years ago

OrientDB is Multi-Model database supports document, graph and key/value data stores. Can you provide a high level steps on how to write the adapter? I can start developing it.

1602 commented 11 years ago

Take one of existing adapters as an example, then start rewriting it to provide interface to your db. Once all imported tests passed - your adapter is ready, write specific tests to cover some tricky logic related to database. I would recommend to start with mongodb adapter as example of simple adapter. For more complicated example - check redis-hq adapter. If you need SQL syntax - check one of sql adapters (mysql, postgres, sqlite).

ghost commented 11 years ago

I'm interested in this as well, and can help cut some code. Is there a plan on how to handle graph dbs in general? I'm wondering if there's room for an additional set of classes in schema.js to load in support for vertexes and edges.

The Neo4j adapted mixes in classes & methods to handle these but I'm thinking that basic support for vertex/edges would be better suited in the core.

kesavkolla commented 11 years ago

I agree with you. The existing Neo4j adapter doesn't use the graph model. I'm also looking forward to see support vertex/edge graph model and some support for graph queries.

dgsan commented 11 years ago

I'm not sure about putting graph support in jdb core, but I recently made an attempt at a MySQL specific Enum type that only requires JDB core to allow objects and not just functions as types, with the rest living in the MySQL adapter: https://github.com/1602/jugglingdb/pull/296 https://github.com/jugglingdb/mysql-adapter/pull/39

It seems (offhand) as though a similar approach might work a graph database, allowing for the definition of vertex and edge as full-blown objects (and not just functions) while allowing them to remain adapter specific.

The MySQL adapter also has a Point type, but it's very basic and I'm not much familiar with its usage.

Anyway just some commentary. I know next to nothing about Neo4j or OrientDB, so take it with a grain of salt. And the fact that my pull request could easily get rejected.

marcominetti commented 10 years ago

Hi there, any updates on this feature?

sarhugo commented 9 years ago

About orientdb please check #413