Re: OOP/OOD Philosophy
- From: Michael Feathers <mfeathers@xxxxxxxxxxxxxxxx>
- Date: Sat, 09 Jul 2005 12:57:12 GMT
frebe wrote:
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
Well, here's one and it is a very sad tale. I once worked with a team that embedded database calls throughout their application. They were all over the place. The vendor raised the licensing rate and they simply could not make money with the product. The team wished that they could break the dependencies on the vendor but the calls were too pervasive. The whole thing ended up with a very expensive rewrite which, by the way, had a good amount of separation between the db and the rest of the app. They learned a very expensive lesson about dependencies.
Michael Feathers author, Working Effectively with Legacy Code (Prentice Hall 2005) www.objectmentor.com
.
- Follow-Ups:
- Re: OOP/OOD Philosophy
- From: frebe
- Re: OOP/OOD Philosophy
- References:
- Re: OOP/OOD Philosophy
- From: Nick Malik [Microsoft]
- Re: OOP/OOD Philosophy
- From: topmind
- Re: OOP/OOD Philosophy
- From: Robert C . Martin
- Re: OOP/OOD Philosophy
- From: topmind
- Re: OOP/OOD Philosophy
- From: Robert C . Martin
- Re: OOP/OOD Philosophy
- From: frebe
- Re: OOP/OOD Philosophy
- From: Robert C . Martin
- Re: OOP/OOD Philosophy
- From: frebe
- Re: OOP/OOD Philosophy
- Prev by Date: Re: OOP/OOD Philosophy
- Next by Date: Re: OOP/OOD Philosophy
- Previous by thread: Re: OOP/OOD Philosophy
- Next by thread: Re: OOP/OOD Philosophy
- Index(es):
Relevant Pages
|
Loading