Hi

i´m looking for the original white paper from E.F.Codd with his 9 (8)
database rules (consistency, transactions or user-management and so
on.....).
Wher can i find this?
Can everybody give me a hint?

greetings
tobias

A quick Google search fill find plenty of relevant material, such as
http://www.itworld.com/nl/db_mgr/05072001/
http://newton.uor.edu/FacultyFolder/...h/Codd12R.html
http://www.itworld.com/nl/db_mgr/09022002/pf_index.html
http://itmanagement.webopedia.com/TE...dds_Rules.html
http://engr.smu.edu/~fmoore/12rules.htm

Note that Codd's relational rules are nothing to do with his later, and
much less respected, OLAP rules.

Codd played a big role in inventing the relational database, so although
his relational rules are rather theoretical, they still have some
limited relevance some 20 years later. They were, in any case, based on
genuine research. On the other hand, he knew almost nothing about OLAP,
and had little to do with creating his 12 or 18 OLAP rules, which were
based on the features of Essbase, whose vendor sponsored the white
paper.


"Tobias Faust" <tobias.faust (AT) gmx (DOT) net> wrote

hi
thank you for your answer.
But i think to know, that the first original rules from codd are 9 or 8
database rules. I dont mean any explicit OLAP rules. And THIS first paper i
search it.
But now i will first check out your given links.
greetings
tobias

This is C.J Date's version of the 12 Rules from AN INTRODUCTION TO DATABASE
SYSTEMS (5th edition) as set forth in pages 389 - 393

0. (Yes, there is a Rule 0!)

For a system to qualify as a RELATIONAL, DATABASE, MANAGEMENT system, that
system must use its RELATIONAL facilities (exclusively) to MANAGE the
DATABASE.

1. The information rule

The information rule simply requires all information in the database to be
represented in one and only one way, Namely by values in column positions
within rows of tables.

2. The guaranteed access rule

This rule is essentially a restatement of the fundamental requirement for
primary keys. It says that every individual scalar value in the database must
be logically addressable by specifying the mane of the containing table, the
name of the containing column and the primary key value of the containing row.

3. Systematic treatment of null values

The DBMS is required to support a representation of "missing information and
inapplicable information" that is systematic, distinct from all regular
values (for example, "distinct from zero or any other number," in the case of
numeric values), and independent of data type. It is also implied that such
representations must be manipulated by the DBMS in a systematic way.

4. Active online catalog based on the relational model

The system is required to support an online, inline, relational catalog that
is accessible to authorized users by means of their regular query language.

5. The comprehensive data sublanguage rule

The system must support a least one relational language that (a) has a linear
syntax, (b) can be used both interactively and within application programs,
and (c) supports data definition operations (including view definitions),
data manipulation operations (update as well as retrieval), security and
integrity constraints, and transaction management operations (begin, commit,
and rollback).

6. The view updating rule

All views that are theoretically updatable must be updatable by the system.

7. High-level insert, update, and delete

The system must support set-at-a-time INSERT, UPDATE, and DELETE operators.

8. Physical data independence

Self-explanatory.

9. Logical data independence

Self-explanatory

10. Integrity independence

Integrity constraints must be specified separately from application programs
and stored in the catalog. It must be possible to change such constraints as
and when appropriate without unnecessarily affecting existing applications.

11. Distribution independence

Existing applications should continue to operate successfully (a) when a
distributed version of the DBMS is first introduced; (b) when existing
distributed data is redistributed around the system.

12. The nonsubversion rule

If the system provides a low-level (record-at-a-time) interface, then that
interface cannot be used to subvert the system (e.g.) bypassing a relational
security or integrity constraint.

Codd also specified nine Structural features, three Integrity features and
eighteen Manipulative features all of which are required as well. I'd repeat
them here but this note is already too long.

hi

you don´t understand me. I know this 12 rules and i know the 9 rules from
codd also. But now i search the original white paper, written by codd, with
his 9 rules. And i think he had not only wrote down his 9 rules, maybe he
had additionaly wrote some elucidations and his thoughts.
I´d like to download his original paper , witten by him.

greetings
tobias

hi again,

i´ve found the exactly description of this paper:

Codd, E.F.: Relational Database: A Practical Foundation of Productivity.
Communications of the ACM, Volume 25, Nr.2, page 109-117, february 1982

where can i find this?

greetings
tobias

"Tobias Faust" <tobias.faust (AT) gmx (DOT) net> wrote

You may have a problem finding a Web version of Codd's original
publication of his relational rules as it was done long before the Web
came along and so was, presumably, never published on the Web. What you
can find quite easily are more modern interpretations and explanations
of what he wrote some 20 years ago. And according to these, his original
publication was a Computerworld article, not a white paper.

His later OLAP rules were published as a white paper, commissioned by
Arbor Software, and that is available on-line from Hyperion Solutions.

On Mon, 1 Mar 2004 15:35:13 +0100, "Tobias Faust"
<tobias.faust (AT) gmx (DOT) net> wrote:

I only want to add that Codd rules are currently considered outdated.
The Third Manifesto is a better source for the rules that a RDBMS must
satisfy.

Regards
Alfredo

hi

has anybody the original publication from the Computerworld article?
Can anybody make a copy with a computerscanner?

freetings
tobias

http://www.acm.org/
and follow these links:

bye
Matteo

------------------------------------
Peggio pe' voi che me ciavete messo!
Silenzio! e rispettate er Presidente!
------------------------------------