Yes, I used this method for a long time by putting code right into the CF codebase. I used a different datasource for the DB updates, one that allowed MODIFY / ALTER / CREATE, and then had the code test against existing DB structures to decide which changes needed to be made along with that set of code changes.
Still always appreciated having those changes made in one DB, but it wouldn't have mattered much because all changes were managed in the same codebase. On 2/23/2011 3:46 PM, Brian Cain wrote: > I wrote a custom desktop application in VB to update all my databases at one > time. Using SQL scripting this can be easily managed. When I am ready to > roll out a change that requires a DB update, I can do it in real time, with > minimal service interruption, and without taking the sites offline. It has > not failed me yet, and I have been doing it that way for over 6 years. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342539 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
