您是否对数据库项目使用源代码管理? [英] Do you use source control for your database items?

问题描述

我觉得我的商店有一个漏洞，因为我们没有一个可靠的流程来对我们的数据库架构更改进行版本控制.我们做了很多备份，所以我们或多或少都被覆盖了，但以这种方式依赖最后一道防线是不好的做法.

I feel that my shop has a hole because we don't have a solid process in place for versioning our database schema changes. We do a lot of backups so we're more or less covered, but it's bad practice to rely on your last line of defense in this way.

令人惊讶的是，这似乎是一个共同的话题.我接触过的很多商店都忽略了这个问题，因为他们的数据库不经常变化，他们基本上只是尽量做到一丝不苟.

Surprisingly, this seems to be a common thread. Many shops I have spoken to ignore this issue because their databases don't change often, and they basically just try to be meticulous.

不过，我知道那个故事是怎么回事.事情出现错误并丢失某些东西只是时间问题.

However, I know how that story goes. It's only a matter of time before things line up just wrong and something goes missing.

是否有任何最佳做法?有哪些策略对你有用?

Are there any best practices for this? What are some strategies that have worked for you?

推荐答案

必读 让您的数据库处于版本控制之下.查看 K. Scott Allen 的系列帖子.

Must read Get your database under version control. Check the series of posts by K. Scott Allen.

说到版本控制，数据库往往是二等甚至三等公民.从我所看到的情况来看，一百万年后永远不会想到编写没有版本控制的代码的团队——而且确实如此——可能会以某种方式完全忘记围绕他们的应用程序所依赖的关键数据库进行版本控制的需求.我不知道当您的数据库与其他代码的源代码控制级别不同时，您如何称自己为软件工程师并保持板着脸.不要让这发生在你身上.让您的数据库处于版本控制之下.

When it comes to version control, the database is often a second or even third-class citizen. From what I've seen, teams that would never think of writing code without version control in a million years-- and rightly so-- can somehow be completely oblivious to the need for version control around the critical databases their applications rely on. I don't know how you can call yourself a software engineer and maintain a straight face when your database isn't under exactly the same rigorous level of source control as the rest of your code. Don't let this happen to you. Get your database under version control.

这篇关于您是否对数据库项目使用源代码管理?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！