Re: the relational model of data objects *and* program objects
From: Kenneth Downs <knode.wants.this_at_see.sigblock>
Date: Wed, 13 Apr 2005 09:21:27 -0400
Message-Id: <k1jvi2-ou7.ln1_at_pluto.downsfam.net>
>
> Spreadsheets and even SQL DBMSs are very different beasts, as has been
> described over and over again in these pages, and relational is
> different yet. If you're placing spreadsheets, relational, and SQL all
> in the same category, then there's not much left to discuss, I suppose.
>
> - erk
Date: Wed, 13 Apr 2005 09:21:27 -0400
Message-Id: <k1jvi2-ou7.ln1_at_pluto.downsfam.net>
erk wrote:
>> the row&column model was quite useful abstraction simplification that >> also shows up in the uptake of spreadsheet technology ... and fits >> well with the prevalent paper-based orientation of the period.
>
> Spreadsheets and even SQL DBMSs are very different beasts, as has been
> described over and over again in these pages, and relational is
> different yet. If you're placing spreadsheets, relational, and SQL all
> in the same category, then there's not much left to discuss, I suppose.
>
> - erk
What about the manifest intuitive appeal to the human mind of information stored in tabular format? Given how this organization keeps being reinvented in the forms mentioned above, perhaps we must demote RDM to merely being one of the crowd of tabular organizations, and consider that it may not be whole, complete, infallible and perfect.
New growth will not likely be as extensions to RDM, because it is self-limiting, but could very well come as more insight into what we can do with tabular data.
-- Kenneth Downs Secure Data Software, Inc. (Ken)nneth_at_(Sec)ure(Dat)a(.com)Received on Wed Apr 13 2005 - 15:21:27 CEST