Comments on: Deprecation within Database Schemas http://mauszeig.wordpress.com/2007/09/08/deprecation-within-database-schemas/ Eclipse, GIS development and news from the agile data trenches Thu, 08 Oct 2009 13:24:05 +0000 http://wordpress.com/ hourly 1 By: Scott W. Ambler http://mauszeig.wordpress.com/2007/09/08/deprecation-within-database-schemas/#comment-8683 Scott W. Ambler Tue, 11 Sep 2007 05:36:01 +0000 http://mauszeig.wordpress.com/2007/09/08/deprecation-within-database-schemas/#comment-8683 This is something that Pramod Sadalage and I wrote about in Refactoring Databases, http://www.ambysoft.com/books/refactoringDatabases.html To effectively communicate deprecation within a database you would need to: 1. Automatically support it within the database itself as you imply above. This would imply that the database should throw a low-level warning when you access something that's deprecated. This implies an architectural change to the DB itself, something that the vendors would need to do. 2. Support deprecation within physical data models. I've also proposed UML modeling notation for that at http://www.agiledata.org/essays/umlDataModelingProfile.html, a notation that we use in the book. This is something that the data modeling tool vendors would need to support. 3. Get people working in this sort of manner. This requires a cultural change, something which always takes time. - Scott Practice Leader Agile Development, IBM Rational This is something that Pramod Sadalage and I wrote about in Refactoring Databases, http://www.ambysoft.com/books/refactoringDatabases.html

To effectively communicate deprecation within a database you would need to:
1. Automatically support it within the database itself as you imply above. This would imply that the database should throw a low-level warning when you access something that’s deprecated. This implies an architectural change to the DB itself, something that the vendors would need to do.
2. Support deprecation within physical data models. I’ve also proposed UML modeling notation for that at http://www.agiledata.org/essays/umlDataModelingProfile.html, a notation that we use in the book. This is something that the data modeling tool vendors would need to support.
3. Get people working in this sort of manner. This requires a cultural change, something which always takes time.

- Scott
Practice Leader Agile Development, IBM Rational

]]>