On 10 June 2010 12:00, silky <[email protected]> wrote: > I know there was a thread on this recently. The versioning inside the > DB is obviously one component of this, but scripting the changes is > the other part. > > Does anyone automate the scripting? It seems to me that it would be > cool if you had a command-line tool that scripted the latest changes > to local DB that you were working with (i.e. configurable in some > script) and then saved those changes to a file as part of a > source-control commit operation. That is to say, you'd script this > tool as a pre-commit operation (locally, I think most source control > systems support this kind of operation). > > I'm pretty sure someone on this list has such a tool. I can't quite remember. > > Anyone taking this approach? Is it a good idea?
Something like Redgate? http://www.red-gate.com/products/SQL_Compare/index.htm > > The reason I like it is because I don't have to make the script myself > (which is trivial but boring) and it means I won't miss anything. > Obviously significant configuration of the tool would be appropriate > (and a chance to perhaps review the script before it was committed). > It would be good because it's kind of extravagent to have > individually-held files for each DB item. Perhaps not. > > -- > silky > > http://www.programmingbranch.com/ > -- Meski "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
