Re: Put code inside or outside database?

On 8 Apr 2005 06:45:19 -0700, "GeoPappas" <PappasG_at_gmail.com> wrote:

I stick pretty much with the ROTS.

Heavy database calls in PL/SQL. C programs (PROC) can call PL/SQL code.

Heavy compututation done in C, Java, etc (PL/SQL native compilation in 9i and above performs computations much closer to native calls!)

We are a heavy DOTNET shop. If you set the COMMANDTYPE attribute to STORED PROCEDURES instead TEXT then you can call PL/SQL from DOTNET programs. This is a best practice! Developer must learn to use REF CURSOR.
>I was wondering what your opinion on this subject was...
>
>You can place application code in various places. There are three main
>camps (that I see):
>
>1. Put all (or most) of the application code outside the database
>(e.g., in Java or .NET on an app server).
>
>2. Put all (or most) of the application code inside the database (using
>PL/SQL, stored procedures, and triggers).
>
>3. Use a combination of 1 and 2. In other words, put some code outside
>the database, and some code in the database.
>
>What does your place of employment currently do? What do you think is
>the "best practice"?
>
Received on Sun Apr 10 2005 - 19:35:54 CDT