Re: OOP - a question about database access

"Uncle Bob (Robert C. Martin)" <u.n.c.l.e.b.o.b_at_objectmentor.com> wrote in message news:<ig2lqvsfbjjhcniov8lskbdpogkd2oagvb_at_4ax.com>...

> >Objects like Employee, Customer, etc are completely unnecessary
> >because that entities are already managed by the DBMS. You only need
> >to map the database tables to visual controls like grids, edits, etc.
>
> This might be true if the database application does absolutely not
> processing of the data. If there are no business rules, and the
> system does nothing more than add, display, modify, and delete
> records, then having entity objects may not be very useful. On the
> other hand, as soon as you add any business rules, such as field
> validation, or summary reporting, etc. you need a way to separate
> those rules from the database. That's one very useful application for
> OO.

What a pearl!

Sorry for the crossposting again, but I find things like this interesting in order to understand the current state of the IT industry.

If recognized OO writers show this "understanding" of the data management issues, imagine the rest.

Alfredo Received on Fri Nov 07 2003 - 14:04:34 CET