Re: SQL

> If we ignore the persistence aspect, what remains is the organization of
> data according to the relational model. That's certainly useful, but it's
> not 'MANY' features.

Here are my top four non-persistence related features that I use every
day. I think they are very important.
* Queries.
* Transactions.
* Referential integrity
* Caching.

> Nevertheless, persistence is considered one of the cornerstones of
> RDBMS:es, and one thing that RDBMS:es are expected to offer.
Do do you have anything to back it up with?

> However, if you look around, I think you will see that the
> _vast_ majority of uses of databases are, in fact, for _persistent_
> storage of data.
Only in the OO world. In the rest of the world there are many examples
of the opposite.

Fredrik Bertilsson
http://butler.sourceforge.net

.

Relevant Pages

  • Re: SQL
    ... >> If we ignore the persistence aspect, what remains is the organization of ... >Here are my top four non-persistence related features that I use every ... Those I'd generally consider to be part of the relational model - the ... you have any examples of relational databases that have specific features ...
    (comp.object)
  • Re: SQL
    ... >>>solution to persistence access that is designed around a particular ... > create a RAM-based RDB and use SQL to access it with no persistence. ... You agree that the relational model is not only about persistence? ...
    (comp.object)
  • Re: SQL
    ... solution to persistence access that is designed around a particular model of persistence itself. ... provide any pointer showing that the relational model is supposed to be a "persistence model". ... Note that I was careful to say that SQL is a solution to persistence /access/ when the data is represented in RDB form. ...
    (comp.object)
  • Re: SQL
    ... persistence is one of MANY features of a DB. ... > or less) to the relational model, and and it does so in a persistent ... >>> databases. ...
    (comp.object)