| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: What databases have taught me
topmind wrote:
> Neo wrote:
>
>>>As some are pointing out now, OOP designs to not have to be hierarchical. However, outside of hierarchies, OO tends to lose its selling point. It is just a bunch of nodes (objects) with pointers to link them up, a big graph. >> >>I agree. In cases where data is highly structured, representing them >>with a RMDB provides many advantages. However in cases where data is >>highly unstructured, representing them with a RMDB can also become more >>difficult and starts to lose some of its advantages.
As Fabian Pascal points out, information devoid of structure is noise. Without structure, data can have no perceptable meaning.
> One can dump everything into an "attribute table" if there is no
> classification or "slot" for something, for example. Arbitrary graphs
> with arbitrary attributes can be created using a couple of many-to-many
> tables. If you really want a big blob of sloppy or
> inconsistently-labelled stuff, relational can model such. (Many
> on-server file systems I encounter are such messes, for example.
> Perhaps this is why the likes of Google exist.)
>
> However, I am not saying that relational is best for every structuring
> need; just the majority of what I encounter in my domain.
I think the focus on structure to the exclusion of manipulation is a mistake. Presumably, if you think a different formalism sometimes surpasses the relational model, the formalism must provide manipulation as well as structure. What formalisms are you thinking of? Received on Fri Jun 23 2006 - 19:58:31 CDT
![]() |
![]() |