Re: Oracle Financials

From: Srinivas Chintamani <srinivas.chintamani_at_gmail.com>
Date: Wed, 3 Mar 2010 19:53:02 -0500
Message-ID: <98c5e2a21003031653s581c2ed3t8b8364585d297662_at_mail.gmail.com>



WOW! that was good response !

On Wed, Mar 3, 2010 at 11:25 AM, Niall Litchfield < niall.litchfield_at_gmail.com> wrote:

> Before we go too far down this route it's worth considering how one would
> design an application back in the days when customers didn't have access to
> declarative referential integrity, PL/SQL was new and the cutting edge
> version of the database was marketed with an added cost "transaction
> processing option". Queries were 'optimized' using a set of rules and the
> number of concurrent users was frequently less than 20. Even the decision
> not to normalize when normalization meant you had to do your own data
> integrity wasn't as terrible as it might have been.
>
> None of the above should of course excuse SOA :)
>
> Niall
>
> On Wed, Mar 3, 2010 at 3:26 PM, Jared Still <jkstill_at_gmail.com> wrote:
>
>> On Wed, Mar 3, 2010 at 7:17 AM, Kellyn Pedersen <kjped1313_at_yahoo.com>wrote:
>>
>>> ...
>>> "build us a financial application" but forgot to let them in on the
>>> 10 commandmants of Oracle, (i.e. thou shalt not build complex views upon
>>> complex views, though shalt not index every column in a table,....:))
>>>
>>>
>> thou shalt not forget the purpose of normalization
>>
>> Jared Still
>> Certifiable Oracle DBA and Part Time Perl Evangelist
>> Oracle Blog: http://jkstill.blogspot.com
>> Home Page: http://jaredstill.com
>>
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>

-- 
Regards,
Srinivas Chintamani

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Mar 03 2010 - 18:53:02 CST

Original text of this message