This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes book expectations... (refactoring databases) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "book expectations... (refactoring databases)" Watch "book expectations... (refactoring databases)" New topic
Author

book expectations... (refactoring databases)

manuel aldana
Ranch Hand

Joined: Dec 29, 2005
Posts: 308
what i find always difficult with schema changes is that is has the biggest possible impact on the whole application, because data is the brain and the main thing (enterprise) applications are relying on.

that means you have to change lots of things:
- domain model, which often maps more or less directly to the schema
- view components (e.g. webapp struts or jsf beans)
- business layer, which is working on or passing around data
- migration of old data to the new schema

so i think changing the data-model is the most expensive thing you can have, and that's why many hardly do data model changes, though it is often the most neccessary thing to do. i always get

so my questions to the authors or people who know this book:
1) does this book discuss above difficutlties?
2) is it totally focused on relational databases or does it discuss other database approaches too (OODBMS, XMLDBMS)?

thanks.
[ July 25, 2006: Message edited by: manuel aldana ]

aldana software engineering blog & .more
Scott Ambler
author
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
so i think changing the data-model is the most expensive thing you can have, and that's why many hardly do data model changes, though it is often the most neccessary thing to do.


Yes, it's necessary so you need to get good at it. That's what this book is all about, we're bringing a common coding technique to the data community (finally!).

The greater the coupling, the greater the difficulty of refactoring something. We definitely talk about this, and highly suggest that you encapsulate database access so as to reduce coupling.

so my questions to the authors or people who know this book:
1) does this book discuss above difficutlties?
2) is it totally focused on relational databases or does it discuss other database approaches too (OODBMS, XMLDBMS)?



The focus is completely on relational databases.

- Scott


<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
 
GeeCON Prague 2014
 
subject: book expectations... (refactoring databases)