java - Storing parent-child relationship in MarkLogic -


for marklogic (and maybe nosql in general?), best store parent-child 1 document? thus, if coming relational world, normalized parent-child table need denormalized , stored single document?

will design impact how searches done (since children records searched in context of parent)?

it might depend whether children can have multiple parents or not (e.g. graph-type data, instead of hierarchical), reasoning hierarchical data, storing in natural hierarchical form (using xml or json or such), makes sense. doesn't mean storing entire parent-child table 1 document, rather expanding records original trees, , storing documents.

this not fit nosql solutions, work fall document store category, particularly if provide search around contents , hierarchy.. marklogic..

note: graph-type data can stored triples inside marklogic. allow querying sparql, , inferencing on instance..

hth!


Comments

Popular posts from this blog

sequelize.js - Sequelize group by with association includes id -

android - Robolectric "INTERNET permission is required" -

java - Android raising EPERM (Operation not permitted) when attempting to send UDP packet after network connection -