Re: OOP/OOD Philosophy

> Post development, with the same version, just how often do you plan to "add
> a column"?
I make new versions of my applications and add columns all the time.
For example my current project, an time reservation application.
Yesterday got a customer request that there need to be a limit of how
many reservations a user can make, otherwise the application can be
misused. This forces me to add a new column to the configuration table.

> How unstable is your application?
All applications are changing, otherwise they have no users.

> BTW, your terminology presumes an RDB underlying everything.
Correct

> I do not.
Why not?

> Do you not plan to use design and project management, or just randomly "add a column"?

Adding of a column is planned in a new version, of course. But new
versions may be release every month.

> So long as the interfaces do not change, a change in one layer does
> NOT mandate a change anywhere else.
No, but a change in the database schema will most likely also change
the business layer.

>> Can you give some examples of such scenarios?
>Please see above.
I did not find any examples.

Fredrik Bertilsson
http://butler.sourceforge.net

.

Relevant Pages

  • Re: What is an OODBMS?
    ... > the key differences between the RDB view and OO applications. ... Isn't the main reason why the old database paradigm was abandoned, ... > then one will have to have explicit selection logic for that. ... Does this logic belong to the "business layer" or the "persistence ...
    (comp.object)
  • System Architecture / .NET Remoting
    ... I'm working on creating a SOA for my applications. ... numerous .NET IIS applicaitons. ... Placing the business logic into stored procedures seems like an easy ... that business layer. ...
    (microsoft.public.dotnet.languages.csharp)