简体   繁体   English

使用 ArangoDB,具有 x 个边定义的 1 个命名图与具有 1 个边定义的 x 个命名图之间的实际区别是什么?

[英]With ArangoDB what is the practical difference between 1 named graph with x edge definitions vs x named graphs with 1 edge definition?

Is the difference only logical / housekeeping related?差异仅与逻辑/内务管理有关吗?

I did read this question but the answer there only deals with 1 edge definition vs multiple edge definitions within a graph which is now already covered in the documentation .我读过这个问题,但答案只能有1个边缘清晰度VS现在已经覆盖了在图形中的多个边缘定义涉及文档 So I'm curious.所以我很好奇。

I have used Arango for 6 years and don't use Graph objects, all my queries are just AQL queries, which means you don't need to use a Graph to use the benefits of graph databases and to perform traversals.我已经使用 Arango 6 年了,没有使用 Graph 对象,我所有的查询都只是 AQL 查询,这意味着您不需要使用 Graph 来利用图数据库的好处并执行遍历。

The way I think of a 'Graph' in Arango is that it's a limited / curated view of your collections that is query-able, but also is helpful if you want it to manage some level of integrity on deletes.我认为 Arango 中的“图表”的方式是,它是可查询的集合的有限/精选视图,但如果您希望它在删除时管理某种程度的完整性,也很有帮助。

Overall, it slows down a Traversal, so I find it better to avoid them.总的来说,它会减慢遍历速度,所以我发现最好避免它们。 A key driver for my decision is that I don't need views, and I don't need the system to handle the deletion of edges if I delete a connected vertex, but that's just my use case.我决定的一个关键驱动因素是我不需要视图,如果我删除一个连接的顶点,我不需要系统来处理边的删除,但这只是我的用例。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM