1 個回答
- 最新
- 最多得票
- 最多評論
2
Neptune is a "schema-on-read" database and does not provide a way to define a schema or constraints. That being said, there are one or two built-in constraints that you can take advantage of:
- If using Neptune to store Property Graphs, every node and edge must have a unique ID. You can use this to your advantage if there are concepts in your data that must be unique.
- Every edge must have a node at either end of the edge. You cannot have "dangling edges". This ensures that when you delete a node, all adjacent edges to the node are also deleted.
已回答 3 個月前
相關內容
- 已提問 10 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 4 年前