RE: Primary Keys optional?
- From: "Yasin Baskan" <yasbs@xxxxxxxxxxxxxx>
- To: <wbfergus@xxxxxxxx>, "Khemmanivanh, Somckit" <somckit.khemmanivanh@xxxxxxxxxxxxxxxx>
- Date: Fri, 18 Aug 2006 09:53:59 +0300
Besides, having validation and integrity in the database has important
performance improvements. Primary keys and referential integrity helps
the cbo to take cleverer actions and produce better plans. I do not have
a test case for that now but i remember lots of them at the asktom site.
Or we must ask Jonathan Lewis about that :-)
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of William B Ferguson
Sent: Thursday, August 17, 2006 11:45 PM
To: Khemmanivanh, Somckit
Cc: andert@xxxxxxxxx; jkstill@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx;
oracle-l-bounce@xxxxxxxxxxxxx
Subject: RE: Primary Keys optional?
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@xxxxxxxxxxxxxxxx>
08/17/2006 02:39 PM
To
<wbfergus@xxxxxxxx>, <jkstill@xxxxxxxxx>
cc
<andert@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>,
<oracle-l-bounce@xxxxxxxxxxxxx>
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...
Bu mesaj ve onunla iletilen tum ekler gonderildigi kisi ya da kuruma ozel ve
Bankalar Kanunu geregince, gizlilik yukumlulugu tasiyor olabilir. Bu mesaj,
hicbir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para
karsiligi satilamaz; mesajin yetkili alicisi veya alicisina iletmekten sorumlu
kisi degilseniz, mesaj icerigini ya da eklerini kopyalamayiniz, yayinlamayiniz,
baska kisilere yonlendirmeyiniz ve mesaji gonderen kisiyi derhal uyararak bu
mesaji siliniz. Bu mesajin iceriginde ya da eklerinde yer alan bilgilerin
dogrulugu, butunlugu ve guncelligi Bankamiz tarafindan garanti edilmemektedir
ve bilinen viruslere karsi kontrolleri yapilmis olarak yollanan mesajin
sisteminizde yaratabilecegi zararlardan Bankamiz sorumlu tutulamaz.
This message and the files attached to it are under the privacy liability in
accordance with the Banking Law and confidential to the use of the individual
or entity to whom they are addressed. This message cannot be copied, disclosed
or sold monetary consideration for any purpose. If you are not the intended
recipient of this message, you should not copy, distribute, disclose or forward
the information that exists in the content and in the attachments of this
message; please notify the sender immediately and delete all copies of this
message. Our Bank does not warrant the accuracy, integrity and currency of the
information transmitted with this message. This message has been detected for
all known computer viruses thence our Bank is not liable for the occurrence of
any system corruption caused by this message
Other related posts:
