RE: Primary Keys optional?

From: William B Ferguson <wbfergus_at_usgs.gov>
Date: Thu, 17 Aug 2006 14:44:40 -0600
Message-ID: <OF286F7C6E.B27FA218-ON872571CD.0071AC9D-872571CD.00723F51@usgs.gov>

It's rarely good practice to ever depend on an application for data validation and integrity. Things (and applications) change.

Depend on the database for these simple and basic steps instead of the application. And, if the application does do data validation and integrity, nothing is broken anyway by enabling it at the database level.

                               Bill Ferguson
            U.S. Geological Survey - Minerals Information Team
                           PO Box 25046, MS-750
                           Denver Federal Center
                          Denver, Colorado 80225
           Voice (303)236-8747 ext. 321     Fax   (303)236-4208
      ~ Think on a grand scale, start to implement on a small scale ~

"Khemmanivanh, Somckit" <somckit.khemmanivanh_at_weyerhaeuser.com> 08/17/2006 02:39 PM

To
<wbfergus_at_usgs.gov>, <jkstill_at_gmail.com>
cc
<andert_at_gmail.com>, <oracle-l_at_freelists.org>,
<oracle-l-bounce_at_freelists.org>

Subject
RE: Primary Keys optional?

Could the data validations/verification be done at the App level? Of course, the developers should have know this if that were the case...

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Aug 17 2006 - 15:44:40 CDT