Database Reference
In-Depth Information
Figure 2.7. A
User
with some properties
There may be some scenarios in which this is exactly the right way to model a user and
their properties, but there are some warning signs here. If you see a relationship labeled
has_property
or similar, consider whether the node on the other end of the connection
really needs to be a node. Unless, for some reason, you wanted to link users together based
on their favorite colors, there's probably no need for
FavoriteColor
to be modeled as
a node; it could be an property on the
User
node. The same is true for the
name
and
age
properties.
If you convert these nodes into properties on the
User
node, and rename the remaining
has_property
relationship so that it more closely describes the relationship the
User
