Re: Oracle Unit Testing

On Sat, 03 Feb 2007, niall.litchfield_at_dial.pipex.com wrote:

> Second, how many applications access your data, now and in the future?
> If this number is more than 1 then do you replicate the business rules
> n times, once for each application, or do you make them all go through
> the same application? Forever. If it's exactly 1 application that
> accesses this data, then it is likely not a real world
> application. most of us have reporting requirements, interface
> requirements, bits of functionality that would be good elsewhere and
> so on at the very least, but often several entirely different
> applications with the same data store. Abstracting everything away
> from the database is a great way to ensure developer employment.

Don't let facts get in the way of writing object oriented systems.

Here's a side note. Database independence has dwarfed into database ignorance. The java tier is so enamored with how "beautiful" reflection makes their development world that they don't even open up sqlplus. They won't code a single proc or sql statement. For me, this whole world has given me more job security. I'm the database guy supporting a host of java folks that can't code anything more complicated than a simple select? They are completely dependent on me.

-- 
Galen Boyer