We are trying to get the most tight integration with graphdb as possible in the basic blueprint of this framework. We are using neomodel python library to map Graph nodes&relationships to Python Classes.
Also great news, neomodel will support the latest neo4j 3.0 native python driver, see the issue i opened here. Until then we will stick with version 2.3.3.
Models should be made customizable, for the moment the base version is in some kind of limbo, between backend and vanilla code.
On the backend side some things should be done to verify what is the best way to handle connections and models injections. I expect this to be on @mdantonio shoulders, and @dpaoletti could help to get some understanding of the graphdb as well.
We are trying to get the most tight integration with graphdb as possible in the basic blueprint of this framework. We are using
neomodelpython library to map Graph nodes&relationships to Python Classes.Also great news, neomodel will support the latest neo4j 3.0 native python driver, see the issue i opened here. Until then we will stick with version 2.3.3.
Models should be made customizable, for the moment the base version is in some kind of limbo, between backend and vanilla code.
On the backend side some things should be done to verify what is the best way to handle connections and models injections. I expect this to be on @mdantonio shoulders, and @dpaoletti could help to get some understanding of the graphdb as well.