您对数据库项目使用源代码控制吗？ [英] 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屋！