How does /prog/ handle source control for database changes? I have a DB that changes pretty frequently based on customer requests, and I'm having trouble coming up with a scheme that would handle changes to stored procedures, lookup data, table definitions, etc. Bonus is getting it to handle both full build scripts as well as incremental patches.
inb4 lmgtfy.com, I don't know how to google.
Name:
Anonymous2009-09-27 15:31
The only time I ever did this, I just used regular version control with a sql dump of the database. Not the best solution, perhaps, but it served my needs fine.
>>1
There isn't any quick answer to solve your problem. The only way is to restructure your system to meet your requirements. http://mitpress.mit.edu/sicp/
>>1
That is an excellent question, and makes it painfully clear that database designers are anything but programmers.
Name:
Anonymous2009-09-28 17:19
Take this keyboard, and take it to the captain..ha
Take this keyboard, and take it to the captain..ha
Take this keyboard, and take it to the captain.......ha
Tell him i'm gone
Tell him i'm gone
Name:
Anonymous2009-09-28 21:23
>>1
Try useing a vesion control system like cvs or subversion
Actually I really have no idea. My boss is perpetually angry at me because I'm making no attempt to integrate a migrations framework into our ORM. My post is half in jest; I really do just alter table when I want to migrate. So I am less than useless here.