跟踪图数据库中的历史记录
我正在研究使用图形数据库（例如 Neo4j - 主要是因为我需要 python 绑定）来建模真实的物理网络。然而，要求之一是能够跟踪机器所在位置的历史记录、网络端口的状态等。
在关系数据库中，我可以很容易地创建一个“存档”表，我可以用它来执行历史查询，然而，我已经多次被固定表模式的问题和到处都是相当尴尬的左连接所困扰。
有人对如何最好地维护图形数据库中的历史关系和节点属性有任何建议吗？
I am investigating the use of a graph database (like Neo4j - mainly because I need the python bindings) for modeling a real physical network. However, one of the requirements is to be able to track the history of where machines were, the state of network ports etc.
In a relational database, I can quite easily create an 'archive' table that I can use to do historical queries, however, I've been bitten many times with the issues of fixed table schemas and rather awkward left joins all over the place.
Does any one have any suggestions on how it would be best to maintain the historical relations and node properties in a graph database?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
根据节点数量，您也许能够拍摄图网络的快照。然后为每个节点建立索引，以便您可以在网络的每个修订版中查询它。
您还可以尝试对每个节点进行版本控制。每次节点或其顶点之一发生更改时，都会复制该节点并引用其所连接的每个节点的当前版本。然后调高刚刚修改的节点的版本号。
Depending on the number of nodes, you might be able to take snapshots of the graph network. Then index each node so that you can query it in each revision of the network.
You could also try versioning each node. Each time a node or one of its vertices changes, copy the node with references to the current version of each node it connects to. Then up the version number of the node you just modified.
由于 Neo4J 基于文件系统，因此您可以通过 Git 轻松保留图形数据库的版本。然后在版本之间来回查看图表的情况等。
Since Neo4J is based on a file system, you can easily keep the versions of your graph database via Git. Then go back and forth between versions to see how the graph was etc.
我知道 Sones 在数据库中提供版本控制。
“...将它们置于版本控制之下并管理各种版本...” 链接
I know that Sones provides version control within the database.
"... place them under version control and administer various editions ..." Link