RE: DB2

["Walden H. Leverich III" <WaldenL@xxxxxxxxxxxxxxx>]

>From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx] 
>...is the primary rule that is broken and will
>probably always be broken in DB2/400

I'm not sure that disqualifies DB2/400 as relational. It just means that you
_can_ setup a situation where you violate the rule, not that you must.
Likewise, if you don't use contraints it's easy to bypass the integrity
between tables, but if you do use contraints they you can't bypass the
integrity.

Just another case where the iSeries provides us with the flexibilty to get
the job done!

-Walden

PS. Damn, I almost sound like an iSeries bigot <G>

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx] 
Sent: Thursday, March 13, 2003 12:57 PM
To: Midrange Systems Technical Discussion
Subject: RE: DB2


> From: Leif Svalgaard
>
> Criteria for Fully Relational

Rule 2, guaranteed access, is the primary rule that is broken and will
probably always be broken in DB2/400, because any non-keyed physical file by
definition fails.  In most "true" RDBs, you'll see a special "row ID" field
that is used to provide a unique key to every row in the table; without
this, the database is not truly relational according to Codd.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.