Re: foundations of relational theory?

"byrmol" <member27348_at_dbforums.com> wrote in message news:3566592.1068113078_at_dbforums.com...
>
> > I might start from perfection with the most
> > perfect paints and brushes when I paint my living room, but if I'm a
> > poor painter (practitioner) it wouldn't matter at all. On the other
> > hand, a master craftsman can work with his 10year old battered brush
> > and leftover paint and do better.

This master prefers his 33 year old battered brush: the relational model. It was well-used before I ever picked it up.

> > And set/relational theory decomposes data into its fundamental
> > particles
> > - like Physics decomposes matter into quarks and leptons. But there is
> > also the "theory of emergent complexity", which says that you just
> > CANNOT explain things like atoms, chemistry, and biology (heck, even
> > classical physics!) in terms of fundamental particles.
>
> Are you trying to say that set/relational theory can lead to chaos?

Whoever he is, he doesn't have a clue what he is trying to say. He is stupid and ignorant; he talks only to hear himself speak.

> > This model has the advantages of Forced Data Integrity, the
> > end user does not have to know our data model.

If he refers to Pick, he doesn't know what data integrity is. He lacks a clue--any clue.

> > Essentially it creates
> > customized mini-sql engines for our data objects.

Really? These mini-engines can compile SQL? Optimize query plans and execute those plans? Incredible.

> > As I study this
> > model more and play with it with Microsoft .net, Disconnected
> > datasets, and XML data sets, I really feel this is the future.

The ignorant and the stupid substitute feeling for thought.

> This quote gave me a good chuckle, because I am currently on a project
> that does this. Nearly the entire enterprise's schemas are replicated
> outside the DBMS's into these XML schema (XSD) for validation before it
> hits the data tier.
>
> Guess what happens... Any DB change HAS to be reflected in the middle
> tier. The middle tier has become a memory hungry, CPU churning pig with
> the added bonus of wiping out all logical/physical separation advantages
> that the DBMS had and for good measure coupling the data tier with the
> middle tier....
>
> "Welcome to the dumb future"

Indeed. And they marvel at how quickly they can harness the cart before the horse. Received on Thu Nov 06 2003 - 16:59:42 CET