Lists Home |
Date Index |
Jim Rankin <firstname.lastname@example.org> writes:
<snip>xml shredding discussion</snip>
> So the best way to frame your question is "Does a hierarchical model
or a relational model
> best solve my business problem?" If the answer is hierarchical, it
probably makes sense to
> always store your documents as XML and query/update/insert in-place.
If the answer is
> relational, it may make more sense to store your data relationally and
> XML at the system's boundaries.
I don't think it's an either/or question. As has been pointed out
before, there are relational models that support hierarchical data
There are various compromises that one must make when doing a relational
to hierarchical mapping, but these are just the traditional space/time
complexity tradeoffs that are made in a data management system reframed.
At some point it all comes down to index traversal and how you want to
manage it. There are lots of ways to slice and dice the problem but
they don't fall neatly into relational vs. non-relational.