Re: Oracle Unit Testing

WebCom Systems wrote:
> In terms of maintenance, a highly modular multi-tiered approach of far
> better for maintenance than a flatter 2-teir traditional architecture.

Still arguing n-tier from the late 90's. It's 2007 now..

> The point of multi-tiered applications is that every bit of code is in
> its correct place, DML in the table encapsulation layer, objects in
> the object layer, business logic in the java layer, and so on...

I have two basic objections to your argument here. First up, what added value to the business does the object layer bring, exactly? What can we do as a result of it, that we otherwise could not?

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.

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info/services