Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Python vs. PL/SQL for Oracle work
On Mon, 20 Feb 2006 09:46:32 -0800, Jeff C wrote:
>
> Mladen Gogala wrote:
>> >> Yes, I agree. The OP definitely has that problem. If you want to do >> something in the database, PL/SQL is definitely the right choice.
I teach both Java and PL/SQL for Oracle University (amongst other things) and have found the following to be quite consistent in Oracle's world:
If it makes sense to 'do it in the database':
If it makes sense to do it before it gets to the database:
Sadly, many people want to do it before it gets to the database, and ewnd up with self-inflicted performance/security/audit issues.
When deciding where is the right location - just ask youself how logn the application will be around in the organization, and how long the data will be around. Many applications get replaced after 2-5 years, but the data often lives for at least 7 years to fulfill legal audit requirements.
(If that is the case, why insist on putting the security, auditing and business constraints where they will be tossed in 3-5 years - even though the data will be kept for longer?)
-- Hans Forbrich Canada-wide Oracle training and consulting mailto: Fuzzy.GreyBeard_at_gmail.com *** Top posting [replies] guarantees I won't respond. ***Received on Mon Feb 20 2006 - 13:33:39 CST