Neo4j 中的最佳方法
我目前正在开展一个项目，其中我必须实施通知系统。我真的很喜欢图形数据库，所以我不知道哪种方法是实现这一点的最佳方法。我一直在考虑两个选项：
1-创建通知节点，将它们与具有挂起或读取关系类型的用户相关联。当我插入它们时，我像挂起一样插入它们，当用户读取它们时，我将关系类型更改为读取。
2-创建通知节点，将它们与用户相关联，并向关系添加一些属性...“状态”（待处理、已读）。然后向该属性添加索引。
如果我的方向很好，我不知道，如果您能指出我的方向，我将不胜感激。
提前致谢。罗德里戈
i am currently working on a project in which i have to implement a notifications system. I am a really starte with graphs dbs, so i dont know which would be the best approach to implement this. I have been thinking in two options:
1-Creating notifications nodes, relating them to the user with a relation type pending or read. When i insert them i insert them like pending and when the user read them, i change the relation type to read.
2-Creating notifications nodes, relate them to the user and add some property to the relation..."status" (pending,read). Then add an index to that property.
I dont if i am well oriented, i would appreciate if you could point me in what direction.
Thanks in advance. Rodrigo
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
罗德里戈,
这在一定程度上取决于您期望得到的东西的数量以及您将如何提出要求。我认为类似
USER---READ--->TODAY---->Status1
|
----UNREAD--->TODAY---->Status2
当大量读取状态开始随着时间的推移而累积时，都可以让您对 READ/UNREAD 的状态和一些有关时间或其他的属性进行分组，同时仍然让你询问对它们的遍历...
这行得通吗？
/彼得
Rodrigo,
it depends a bit on what amount of stuff you are going to expect, and how you are going to ask for this. I think something like
USER---READ--->TODAY---->Status1
|
----UNREAD--->TODAY---->Status2
Would both let you group status for both READ/UNREAD and some property regarding time or otherwise, when a lot of read status are starting to accumulate over time, while still letting you ask traversals over them ...
Would that work?
/peter