Persistence Strategies
teverett opened this issue · comments
Could we have support for multiple persistence strategies? For example:
- one node per object and node properties for fields
- one node per object and sub-nodes for fields?
Not sure if that makes sense. Only properties can actually hold data, so subnode for fields doesn't make sense for primitive fields. However, for complex fields, you'd just have a referenced entity which would be mapped to a subnode.
However, what i'm planning to do is to allow single properties to be mapped to sub nodes, so instead of retrieving a property from the node in the persistence context, it would be a relative path.
ok, cool