Table encapsulation
156844Sep 15 2006 — edited Sep 15 2006I'm having an ongoing discussion regarding the technique of table encapsulation, where every insert/update/delete operation on a table is wrapped inside a pl/sql package.
The debate is happening because all business logic is outside the rdb - the database is used solely as a data repository. As a result, the chief architect deems wrapping table accesses in packages as unnecessary, "doubling the maintenance work".
In such a case (where there is no other pl/sql code), are there any good reasons for encapsulation, or indeed any for not doing so ?