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달 전
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 4년 전
- AWS 공식업데이트됨 4년 전