We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Graph databases, such as Neo4J, could be suited for storing relation between recipe, sub-recipe, ingredients, ustensils. https://neo4j.com/developer/data-modeling/ It is also possible to store in multiple DB (mongoDB & Neo4J): https://neo4j.com/developer/mongodb/
pros for graph oriented
The text was updated successfully, but these errors were encountered:
(n:Recipe { directions: [{ instr: "dissoudreXdansYdansZ, argX: bol, argY: { code: "sel", quantity: 1}, argZ: "milk or water" }] })-[:requirement {factor: x} ]->(sb:Subrecipe/Product/Choice)
Sorry, something went wrong.
No branches or pull requests
Graph databases, such as Neo4J, could be suited for storing relation between recipe, sub-recipe, ingredients, ustensils.
https://neo4j.com/developer/data-modeling/
It is also possible to store in multiple DB (mongoDB & Neo4J): https://neo4j.com/developer/mongodb/
pros for graph oriented
The text was updated successfully, but these errors were encountered: