tag:blogger.com,1999:blog-10846234.post112334515441340294..comments2023-06-22T09:51:55.639+01:00Comments on BOBABLOG: Agile software development and Salesforce: The Database Patch Runner: Table Centric ViewsRob Bailliehttp://www.blogger.com/profile/06513796097645814224noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-10846234.post-1123574454191711252005-08-09T09:00:00.000+01:002005-08-09T09:00:00.000+01:00I'm not convinced by the table-centric view either...I'm not convinced by the table-centric view either, it splits up the context of the change too much.<BR/><BR/>It reminds me of a previous job where we had Sybase database scripts split up by type, so a table script, a trigger script, a user scripts, a stored procedure script, etc. It meant than anything other than a very minor change required updating multiple files.<BR/><BR/>These files were under ClearCase (file locking SCM) with about 100 developers in the codebase, so it made for some very difficult changes, more floor walking and talking than coding!Andrew Beacockhttps://www.blogger.com/profile/01039992884679308726noreply@blogger.comtag:blogger.com,1999:blog-10846234.post-1123362379861974232005-08-06T22:06:00.000+01:002005-08-06T22:06:00.000+01:00Thanks for the insight, Rob.The more I think about...Thanks for the insight, Rob.<BR/><BR/>The more I think about it, the more I feel for your functional centric aproach in stead of my initial feeling of table centric version history. I'll start implementing our version control and build automation in September and will definitely have a look at your approach with the additional DDL triggers.<BR/><BR/>Thanks for the great discussions. They were really helpfull in getting a clear pictureAnonymousnoreply@blogger.com