RE: Database programming standards

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Thu, 3 Jun 2004 14:30:06 -0500
Message-ID: <0186754BC82DD511B5C600B0D0AAC4D607B00733@EXCHMN3>

Deen

Usually the DBA doesn't get a chance to tell the development staff where they should put their business logic ;-)

This is normally the province of the architect.

Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Deen Dayal Sent: Thursday, June 03, 2004 1:10 PM
To: oracle-l_at_freelists.org
Subject: RE: Database programming standards

>From what I gathered on this thread so far

I want to summarize with following

Java code should always use bind variables
Any open cursors/connection should be closed/released when the work is finished and when no longer required
Keep the Business logic in the database using stored procs and packs where ever possible to reduce network traffic and to ensure business rules are always enforced.

I want to know from all of you out there: what are the reasons/arguments developers have against #3

In other words are there any genuine practical reasons except what has been mentioned by Mladen about making the app transparent of the RDBMS (which by the way is a very good point, I will bring it up with my management)

Can any body add anything else to the list above?

The application we are about venture on is going to serve a lot of users, at the peak close to 30K and there are going to be a lot of complex business rules and my guess about the size of the DB should be around 500GB

Thanks to all for your help
Deen

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Daniel Fink
Sent: Friday, 4 June 2004 1:54 AM
To: oracle-l_at_freelists.org
Subject: Re: Database programming standards

Gosh, this sounds like a rather heated discussion I had with an expert in the past. His position was that the database was for storing data...only for storing data. No RI, no check constraints, no stored procs, no triggers. His argument was that anything related to business rules belonged in the application layer.

Other bits stripped...

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/

FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html


-----------------------------------------------------------------

----------------------------------------------------------------

Please see the official ORACLE-L FAQ: http://www.orafaq.com


----------------------------------------------------------------

To unsubscribe send email to:  oracle-l-request_at_freelists.org

put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Received on Thu Jun 03 2004 - 14:29:55 CDT