Re: OOP/OOD Philosophy

I asked you " Why would it be suicide to have a coupling between the
GUI and database schema?"

You gave me an example that did not involve any database access at all.
Can you please give me an example of the bad thing with coupling
between the GUI and database schema?

If your example would have any thing to do with a database, maxItem and
totalAmt would be calculated this way:
select max(item) from product
select sum(amount) from product

Fredrik Bertilsson
http://butler.sourceforge.net

.

Relevant Pages

  • Re: OOP/OOD Philosophy
    ... >I asked you " Why would it be suicide to have a coupling between the ... >between the GUI and database schema? ... "The aim of science is not to open the door to infinite wisdom, ...
    (comp.object)
  • Re: OOP/OOD Philosophy
    ... > GUI and database schema?" ... Because that is the definition of coupling: When it's suicide. ...
    (comp.object)
  • Re: OOP/OOD Philosophy
    ... >> I am not disagreeing with the decoupling of the>GUI layout from the database schema ...
    (comp.object)
  • Re: OOP/OOD Philosophy
    ... > I am not disagreeing with the decoupling of the>GUI layout from the database schema ... What are your arguments for decoupling the GUI from the database ...
    (comp.object)
  • Re: OOP/OOD Philosophy
    ... then coupling the GUI to the Schema is suicide; ... Why would it be suicide to have a coupling between the GUI and database ...
    (comp.object)
Loading