Well, take Peoplesoft as an example, 5885 tables with NO referential integrity, no constraints at all, except for all of those NOT NULL constraints. It's the attitude of developers that the logic should be in the application, not the database.=20 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of bill thater Sent: Thursday, June 02, 2005 12:19 PM To: mark.powell@xxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Semi-OT: It's the Code, Stupid! On 6/2/05, Powell, Mark D <mark.powell@xxxxxxx> wrote: >=3D20 > From experience I am surprised when a vendor product does not fall into > the "worst-case" scenario as far as the database design, process, and > code is concerned. it results, i believe, from trying to be "database independent". and that's something i never have agreed with. if the options are available in the database, use them. "database Independence" just lead to bad design, bad code and a bad implementation. --=3D20 -- Bill "Shrek" Thater ORACLE DBA =3D20 shrekdba@xxxxxxxxx=3D20 ------------------------------------------------------------------------ "Zen is not easy. It takes effort to attain nothingness. And then what do you have? Bupkes." -- The Goddess -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l