Database correctness

Thread View: comp.specification

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by John W. Baugh Jr. Mon, 04 Mar 1991 15:55

#337

Author: John W. Baugh Jr.
Date: Mon, 04 Mar 1991 15:55

12 lines
1078 bytes

I'd like some references on what it means for a database (e.g., the
relational kind) to be "correct", the role of "integrity constraints",
and so forth.  Obviously, if one treats a dbms as just an
implementation of a data type then one can define an abstraction
function and do Hoare-style verification.  Otherwise, general dbms
queries may be thought to compromise abstraction by directly accessing
the internal representation (i.e., the database itself).  So what does
one do, just enforce a representation invariant?  Is this what some
call "integrity constraints"?

John Baugh
jwb@cepmax.ncsu.edu

Re: Database correctness

#338

Author: Pablo A. Straub
Date: Mon, 04 Mar 1991 18:34

21 lines
1219 bytes

In article <1991Mar4.155552.27494@ncsu.edu> jwb@cepmax.ncsu.edu writes:
>I'd like some references on what it means for a database (e.g., the
>relational kind) to be "correct", the role of "integrity constraints",
>and so forth. [...]  Is this what some
>call "integrity constraints"?
>
>John Baugh
>jwb@cepmax.ncsu.edu

For a good and readable treatment of integrity constraints see

    C.J. Date, An introduction to database systems, volume 1, Fourth Ed.,
    Addison Wesley, 1986.

Integrity constraints are covered in chap. 12, section 15.4, chapter 17
and sections 19.5 and 19.6.

The second volume (1983) has a chapter devoted to integrity (chapter 2).

Pablo Straub
straub@cs.umd.edu

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads