-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extending the ORM to neo4j #22
Comments
My experience with graph DBs is very limited so I can't say with any degree of certainty. For a RDBMS the implementation should be pretty straightforward. SearchLight uses something like the bridge pattern in a structure similar to: The corresponding files for the current PostgreSQL implementation are: I guess the only question is how easy would be to query the graph DB in a RDBMS manner - and by looking at the Ruby / Rails implementation, seems doable: If you go down this path let me know, happy to help - I'm curious about it. |
@datnamer Did you ever venture down this path or possibly with another graph DB? |
@berzley nope. Ended up not needing to do so. |
How much work would that be?
It has a different querying language and is not a relational dn, but a graph db.
Edit: Maybe I don't need a graph db? I have entities that are related to multiple categories and to each other.
Can this be modelled currently or since tbe relationships will be many to many and there is no multiple inheritance , i would need to add code?
Maybe model composition instead of inheritance to handle the categories?
The text was updated successfully, but these errors were encountered: