Path: newssvr20.news.prodigy.com!newsmst01a.news.prodigy.com!prodigy.com!news.glorb.com!border1.nntp.ash.giganews.com!nntp.giganews.com!local1.nntp.ash.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail
NNTP-Posting-Date: Thu, 29 Apr 2004 07:54:07 -0500
Reply-To: "Laconic2" <laconic2@comcast.net>
From: "Laconic2" <laconic2@comcast.net>
Newsgroups: comp.databases.theory
References: <408a2873$0$563$e4fe514c@news.xs4all.nl> <otydnUJWc6meHhfdRVn-vw@comcast.com> <pan.2004.04.24.17.26.30.638187@dutra.fastmail.fm> <bN-dnVoYIZfUQxfdRVn-vA@comcast.com> <pan.2004.04.26.00.20.42.702517@dutra.fastmail.fm> <v42dncrEGaUNZRHdRVn-jw@comcast.com> <pan.2004.04.27.13.50.08.841038@dutra.fastmail.fm> <y5SdnQL6dKAF6xPd4p2dnA@comcast.com> <pan.2004.04.28.17.23.49.405144@dutra.fastmail.fm>
Subject: Re: c.d.theory glossary - NULL
Date: Thu, 29 Apr 2004 08:55:02 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <hNmdnVMzNbtyZw3dRVn-gw@comcast.com>
Lines: 24
NNTP-Posting-Host: 24.60.68.134
X-Trace: sv3-1oyxqMb9H/VCayqsI66/HApPLWPxaAOa0+ce2m1oXagjgoPeNcVSX9F7OgG+41d/aJUqBBZTSG77LER!sWnPBr9Im+GdauAZOsdImDlBT/gFcapMscpN2+QS3sZnPn9cL1LOeyIzU4uC
X-Complaints-To: abuse@comcast.net
X-DMCA-Complaints-To: dmca@comcast.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.1
Xref: newssvr20.news.prodigy.com comp.databases.theory:26077

> You keep mixing relational and SQL.  SQL ain't relational.

OK,  let's put it this way:

If your task is to build the database for an application,  and your choices
of a DBMS product are limited to Oracle, DB2, SQL Server, or Interbase for
reasons apart from the discussion in here,  and you want to use the RDM as a
basis for your thinking,  here's what you are going to do:

You are going to use tables to represent relations,  and you are going to
use the SQL SELECT to represent relational and set operations on those
tables.

These products have been available for use for some 20 years now, more or
less.  A lot of systems have been built on them.  The ones that use the RDM
as a basis for modeling work better,  in general, than the ones that don't.

If I'm going to present data manipulation operations that represent
relational operations, I'm going to use SQL for the examples.  Until
something better comes along.